Forum > Linux
SETI MB CUDA for Linux
riofl:
I don't understand something. The developers obviously know that cuda devices hate vlar and vhar workunits. why can't they put the smarts that are in the perl script directly into boinc so that as it downloads the workunit it reads the angles etc and decides where to assign it at that point? it should be an easy thing to implement saving lots of trouble for people like me who have a card that locks up at the slightest hint of a vlar and having to run something external to make sure 'proper' workunits are fed to cuda?
seems to me that this ia a gross oversight leaving this out of boinc.
Josef W. Segur:
--- Quote from: riofl on 25 Aug 2009, 09:32:09 pm ---I don't understand something. The developers obviously know that cuda devices hate vlar and vhar workunits. why can't they put the smarts that are in the perl script directly into boinc so that as it downloads the workunit it reads the angles etc and decides where to assign it at that point? it should be an easy thing to implement saving lots of trouble for people like me who have a card that locks up at the slightest hint of a vlar and having to run something external to make sure 'proper' workunits are fed to cuda?
seems to me that this ia a gross oversight leaving this out of boinc.
--- End quote ---
True, the S@H CUDA app has it's greatest advantage for midrange work. The stock BOINC won't be changed as you suggest for the simple reason that it's designed to support common features of use to all projects. BOINC is separate from S@H even though they both derive from Classic S@H in part. OTOH, it's LGPL open source so a special version could be built, feel free to volunteer for that work. ;)
As far as the S@H project providing some additional features, I figure once volunteers begin donating enough money to resolve ongoing problems the staff might be able to find time to work something out. Meanwhile, many of those who have CUDA crunching turned off while using the computer for other things probably don't even notice the difficulty of VLAR. There isn't really any similar issue with VHAR, the main thing there is simply the number of tasks which have to be downloaded when most are VHAR 'shorties'.
Joe
riofl:
makes sense. i keep forgetting about other projects since i only do seti. maybe a shell after the list download would be in order to run a script if it was there. i always find it difficult trapsing around others' code trying to figure out what is what since a majority of the time it is not well commented if at all. i have never looked at boinc source. maybe once they have a stable version that works with multiple devices and properly reports them i might dig in and see what is what. i doubt i would submit mods for this because it would create a separate seti branch of boinc which probably would not be wise. of course, a simple cmdline flag --seti or some such could turn the extra code on or off.. hmm... have to think abit about this.
lordvader:
Hey all.
I recently got a computation error with one of my CUDA WU's, but it wasn't a segfault. Maybe there's some info in there for you guys :
http://setiathome.berkeley.edu/result.php?resultid=1347109626
Raistmer:
--- Quote from: lordvader on 31 Aug 2009, 01:34:21 am ---Hey all.
I recently got a computation error with one of my CUDA WU's, but it wasn't a segfault. Maybe there's some info in there for you guys :
http://setiathome.berkeley.edu/result.php?resultid=1347109626
--- End quote ---
Thanks, but it's known error.
It has even its own sticky thread on main ("-12"). It's some limitation of current CUDA code.
But sometimes such error could appear when card go in broken state.
So if you see many of such errors, then it's equal of many "-9 overflows" that no validated versus wingman => host should be rebooted.
Unfortunately, I have one such buggy card so had chance to see this "-12" for dozens of results at once (usually it's pretty rare error).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version