Windows 7 64-bit, Nvidia Drv v190, BOINC single user install.

----- Rom

-----Original Message-----
From: Raistmer [mailto:[email protected]] 
Sent: Saturday, October 17, 2009 2:33 AM
To: Rom Walton; David Anderson (BOINC)
Cc: [email protected]
Subject: Re: [boinc_dev] BOINC 6.10.14 re missing GPU

What OS & BOINC setup did you use?
Remote desktop not always lead to GPU hiding.
For example, no problem with RDP if OS is Windows 2003 server/XP and
BOINC 
installed as service.
While standalone run of CUDA app under user account will fail in such
case, 
app running under BOINC (running as service) will see GPU and be able to
use 
it.

----- Original Message ----- 
From: "Rom Walton" <[email protected]>
To: "Raistmer" <[email protected]>; "David Anderson (BOINC)" 
<[email protected]>
Cc: <[email protected]>
Sent: Saturday, October 17, 2009 10:13 AM
Subject: RE: [boinc_dev] BOINC 6.10.14 re missing GPU


I just tried to simulate this by using Remote Desktop, and BOINC was
still able to correctly detect the memory information for the Nvidia
GPU.

----- Rom

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Raistmer
Sent: Friday, October 16, 2009 5:52 PM
To: David Anderson (BOINC)
Cc: [email protected]
Subject: Re: [boinc_dev] BOINC 6.10.14 re missing GPU

Don't know if it will work always but in case of "disappeared" GPU


cuMemGetInfo(&free,&total);

returns zero in both fields. Zero in total memory could be sign of
error...

----- Original Message ----- 
From: "David Anderson" <[email protected]>
To: "Raistmer" <[email protected]>
Cc: <[email protected]>
Sent: Saturday, October 17, 2009 1:37 AM
Subject: Re: [boinc_dev] BOINC 6.10.14 re missing GPU


> That's what we're doing.
> We have this working for ATI: the CAL init function fails
> if the GPU is not usable.
> We haven't figured how to tell if an NVIDIA GPU is still working;
> none of the obvious things works.
> We're waiting to hear from NVIDIA on this.
>
> -- David
>
> Raistmer wrote:
>
>> If you really want to improve BOINC's awareness of coprocessor
presence -
>> check this presence itself, not factor that could hide GPU - there
are
>> many such factors.
>> BTW, checking for GPU at moment of schedule decision (if not too
costly
>> by itself) could have additional benefit (additional to correctly
>> handling RDP and fast user switching).
>> There are some situations when GPU just "disappears". Maybe
overheating
>> maybe some another reason, but I see such behavior on one of my
nVidia
>> GPUs, 9400GT.
>> This cause CUDA MB to fallback to CPU processing cause it ordered to
run
>> on GPU but its own check shows no such GPU. This is worse than it
just
>> suspend its work (CPU part of current CUDA MB much worse than
standalone
>> opt CPU MB, hence CPU fallback not only doesn't use GPU, it uses CPU
in
>> inefficient way).
>> If BOINC could check GPU availability before actual task scheduling
it
>> could prevent this situation also.
>>
>> _______________________________________________
>> boinc_dev mailing list
>> [email protected]
>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to