>> Why BOINC should trash whole GPU cache if GPU was not found at current >> BOINC >> start ? >> Why tasks just can't be put in waiting or suspended (to not participate >> in >> scheduling decisions) state until GPU will be available again ? > > Although this code was introduced in response to a trac ticket which > Raistmer himself raised ;-))....
Well, I never proposed to trash tasks! I just pointed out that BOINC hung when GPU was replaced. > Then, yes, I agree that some sort of temporary 'limbo' status is > appropriate, in case it's a simple driver update going wrong. If that's > the problem, normal GPU service is likely to be resumed in half-an-hour or > so - we can afford to hang onto them for that long. It's not most common case. Common case is RDP session to Vista host or multi-user logon to XP/Server host... IMO it will happen much often than driver reinstalls. But sure both cases should be covered (in the same way :) ). > I'm all in favour of user choice and user control. +1 :) _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
