Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1224 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
A previously undocumented cc_config.xml feature for GPU

The chief BOINC developer mailed this today, which I'm sharing as-is. Use it at your own risk, noting that app_info is being mentioned, a part of BOINC that WCG will disable [you can still use it for other projects, if they allow].

Oh, and to emphasize, this is not to be confused with app_config.xml of clients 7.0.42 and up, which is the application level configuration. A cc_config.xml is a global functioning config... it is ignorant of special individual project and application setups.
The client has a GPU-related feature we added a while ago
(> 1 year) but for some reason never documented.
In combination with the anonymous platform mechanism,
it lets you use GPUs not otherwise used by BOINC.

In your cc_config.xml you can specify a GPU that's not used by BOINC -
either a vendor that the client doesn't know about,
or a GPU that the client knows about but decides not to use
because it's less powerful than another one.
The entry looks like this:

<coproc>
<type>some_name</type>
<count>1</count>
<device_nums>0 2</device_nums>
</coproc>

The name (some_name) should be something different from
the names used by BOINC (NVIDIA, ATI, intel_gpu).

In your app_info.xml file, you can list an app version that
will use this GPU.
It should include a <coproc> element using the same name.

For example, if you have several different NVIDIA GPUs in 1 system,
you could have a separate <coproc> element for each one in cc_config.xml,
and specify the apps that can run on each on
in your various app_info.xml files.

This is documented here:
http://boinc.berkeley.edu/wiki/Client_configuration#Options

Let me know if any questions or problems.

-- David

The last line is clear... questions... ask them over at the developers.
[Jan 12, 2013 2:21:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Dataman
Ace Cruncher
Joined: Nov 16, 2004
Post Count: 4865
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: A previously undocumented cc_config.xml feature for GPU

Thanks. That is useful. coffee
----------------------------------------


[Jan 12, 2013 2:27:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: A previously undocumented cc_config.xml feature for GPU

hello

my file cc_config.xml, does not work.

13/01/2013 17:17:00 | | Balise non reconnue dans cc_config.xml: <coproc>

<cc_config>
<coproc>
<type>gpu7970</type>
<count>1</count>
<device_nums>0 2</device_nums>
</coproc>
</cc_config>
[Jan 13, 2013 4:19:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: A previously undocumented cc_config.xml feature for GPU

You've not inserted the required <options> open and </options> close tags around inside of <cc_config>, so it should be at minimum

<cc_config>
<options>
<coproc>
<type>gpu7970</type>
<count>1</count>
<device_nums>0 2</device_nums>
</coproc>
</options>
</cc_config>

Follow instructions per the linked manual in opening post.

but, you really have to ask the developers who did comment that the <type> tag has to be consistent across the different control files
You can choose whatever name you want.
Use the same name in both cc_config.xml and app_info.xml

[Jan 13, 2013 4:29:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread