Markus Dittrich wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 18 May 2007, M. Edward (Ed) Borasky wrote:
Is this applicable to the Gentoo ebuilds?
Hi Ed,
What exactly are you referring to? The part about
ATL_MaxMalloc? If so, I haven't done any benchmarking
yet, but I don't see a problem increasing this
value to 160M as suggested by Clint.
cheers,
Markus
- -- Markus Dittrich (markusle)
Gentoo Linux Developer
Scientific applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGTf8txlRwCwb7k40RAmfSAJ9r5K/RD+4rxJbFm7NDH+ONWoy1ZwCeKLNL
y0jHAOSCmQI+V5mKzcWsjcE=
=LpY6
-----END PGP SIGNATURE-----
Yeah ... I just got an Athlon64 X2 4200+ and the first thing I did when
I got the machine stabilized was build "blas-atlas" and "lapack-atlas"
(3.7.30). New versions of Atlas generally show up in Portage or the
science overlay within a day after Clint releases them, so I don't
usually test the upstream source.
The best I got out of my machine was something like 7 GFLOPS on a 32-bit
test with 3.7.30, and there were some cases that looked like they should
have done better. So I definitely want to test this 160M setting.
--
[EMAIL PROTECTED] mailing list
