1) No backward compatibility. 2) cc_config not part of app_info.xml that supplied for particular project, it's part of whole system setup! And who will do all these changes with cc_config.xml ? User ?
Понедельник, 15 апреля 2013, 20:20 -07:00 от David Anderson <[email protected]>: >The anonymous platform mechanism gives fine-grained control >over how GPUs are used: > >cc_config.xml can include <coproc> elements that describe coprocessor >types (e.g. GPUs). >You pick the name and give the device numbers. >http://boinc.berkeley.edu/wiki/Client_configuration#Options > >app_info.xml can include <coproc> elements saying what coprocessor >type the app version needs. >The <type> can refer to coprocessors specified in cc_config.xml. > >So if you have 1 GPU that can run OpenCL apps and 1 that can't, >put 2 <coproc> elements in your cc_config.xml >(call them, say, ati_opencl and ati_no_opencl). >Set up your app_info.xml so the OpenCL app uses <ati_opencl> >and the CAL app uses <ati_no_opencl> > >Note: these features probably require a version 7 client. > >-- David _______________________________________________ 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.
