This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Tester for openblas needed
- From: "Tony Kelman" <tony at kelman dot net>
- To: <cygwin at cygwin dot com>
- Date: Tue, 21 Oct 2014 05:39:44 -0700
- Subject: Re: Tester for openblas needed
- Authentication-results: sourceware.org; auth=none
- References: <54450C0A dot 6050705 at gmail dot com> <BAY169-DS3454FE83B442F8A23182EBA7970 at phx dot gbl> <54451D4C dot 5080604 at gmail dot com> <BAY169-DS41999173A807A98C0210C7A7970 at phx dot gbl> <54458524 dot 8010603 at gmail dot com> <BAY169-DS201BCE4DCECE478E49F36BA7970 at phx dot gbl> <5445F384 dot 705 at gmail dot com> <544649E9 dot 80808 at gmail dot com>
I avoided to include lapack as for compatibility
I will need to split exactly as netlib in
cygblas-0.dll
cyglapack-0.dll
something for the future.
That makes sense, it gets packaged that way in debian and fedora too.
I think there's an open issue on openblas' tracker to add a build option
to split up the shared library that way, make packagers' lives easier.
Even netlib lapack will run faster with a better blas plugged in, so the
way you're doing it now with just the blas parts makes sense to start with.
So how many THREADS would you like to see ?
I think 8 would cover the majority of users, 16 at the most. I've seen
cases where openblas can try to use threads on small problems where it
shouldn't need to, so it would be good to check whether it's smart about
avoiding oversubscription if you run it without setting
OPENBLAS_NUM_THREADS.
Of course users who really want more threads can compile it themselves,
but it'll be convenient to have a fast blas easily hooked into Cygwin's
packages for numpy, R, octave, etc.
-Tony
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple