A new Linux App is available from our Beta Test page.
Actually it's not a new App at all. The package includes renamed versions of the Apps formaly known as 4.31 and 4.35 and a little wrapper program that switches between them based on the CPU fetures it detects.
If something goes wrong with the automatic switching (i.e. you get "signal 4" "illegal instruction" errors), placing a file named "CPU_TYPE_0" in the BOINC directory should run the generic (non-SSE) App even if the wrapper would detect SSE.
This is a beta test for the wrapper more than anything else. If successful it should enable us to deliver optimized Apps to the larger public that doesn't run "power"- or "beta"-Apps.
The app_info.xml has entries for
420
421
424
427
431
435
438
If your current App version is not listed here, you'll have to add it manually.
BM
BM
Copyright © 2024 Einstein@Home. All rights reserved.
GNU/Linux S5R3 App 4.38 available for Beta test
)
Just successfully started app 4.38 with boinc client 5.10.43!
Hi! Under Knoppix 5.2 I
)
Hi!
Under Knoppix 5.2 I get the following error and the app refuses to run:
RE: Hi! Under Knoppix 5.2
)
Oh yeah - the switcher should be linked statically. Will fix this.
BM
BM
On a system with a more
)
On a system with a more recent libc, all is working fine, tho.
Unfortunately the only non-SSE capable host I've got won't run this one (see above), so I can't really test the CPU detection.
Bikeman
RE: Oh yeah - the switcher
)
Done.
Have another go!
BM
BM
Is there also a Linux 64-bit
)
Is there also a Linux 64-bit version that can tried out?
And has Akos been in on the act for the hot loops?
Looking interesting...
Regards,
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: RE: Oh yeah - the
)
That particular host has run out of quota, but another one (SEE-capable, tho) with an older libc now runs this app without problem.
CU
Bikeman
Since we're talking about
)
Since we're talking about feature detection now, are there any plans to go up to SSE2, or would the costs of doing so outweigh the benefits?
RE: Since we're talking
)
There's still some room for improvements of the SSE code, I'll try that first. My rough guess is that SSE2 would gain less than 10% over the best possible SSE App.
However with the new way of feature-based App switching the "costs" (for the project) are lowered too, compared to the cumbersome mixed-linked Apps we had before.
BM
BM
RE: RE: Since we're
)
Fair enough. There will definitely be diminishing returns on the efforts. If you provide SSE2, then I'm sure people will want SSE3, SSSE3, SSE4, etc... My guess, based on what is being seen with SETI, is that SSE3 is where meaningful improvements would stop. For AMD processors, it became apparent that SSE3 had negligible differences (perhaps due to missing HyperThreading?)...