If some version of the client doesn't report CPU features correctly, please let me know. I'm pretty sure the current version reports them correctly. -- David
On 22-Sep-2010 2:09 PM, yoyo wrote: > I do not remember exactly, but I think Boinc has not properly reported > the cpu capabilities (sse, sse2, sse3, sse4,..) to the server. Therefore > we are going the sam way as einst...@home did. Our app contains versions > for the different cpu capabilities in one zip file. A pre-loader checks > which capabilities the cpu has and extracts the right version. > > yoyo > > Raistmer schrieb: >> Thanks, that just what I need, at least for SSE3 level. >> >> ----- Original Message ----- >> From: David Anderson >> To: [email protected] >> Sent: Thursday, September 23, 2010 12:47 AM >> Subject: Re: [boinc_dev] CPU SSE levels and plan classes >> >> >> This can be done with the plan class mechanism: >> http://boinc.berkeley.edu/trac/wiki/AppPlan >> -- David >> >> On 22-Sep-2010 1:37 PM, Raistmer wrote: >> >>> What "proper" way to configure science app requirements regarding required >>> SSE level of CPU ? >>> That is, does some mechanism exist for BOINC server to judge what >>> executable it should send to BOINC client id BOINC client has SSE2, SSE3 >>> and so on CPU ? >>> AFAIK in some projects (Einstein) generic "stub-app " loaded then some >>> another executable used for corresponding CPU level. >>> It looks like workaround, is it single possible way to account for >>> different CPU capabilities for "stock" science app ? >>> >>> For GPUs we have different plan classes that describe required GPU >>> hardware/sofware capabilities (along with scheduling purposes), what about >>> different CPUs ? >>> _______________________________________________ >>> 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. >> > > _______________________________________________ > 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.
