I forgot to copy my message below to the mailing list.

-------- Message transféré --------
Sujet : Re: [boinc_dev] 'client_state.xml' : GPU info for workunit/result
Date : Sun, 20 Nov 2016 11:51:56 +0100
De : Jean Philippe EIMER <[email protected]>
Pour : David Anderson <[email protected]>

Hi David,

Thank you for your answer.

I agree, I also noticed <app_version> has the info.
But, the <coproc> info is not in <workunit> or <result>.

Below is an extract of my 'client_state.xml'.
You can see there are 2 <app_version> with same <app_name> and <version_num>.
One is with <coproc>, the other without.

The <workunit> below uses an app, which we don't know whether it's the one with coproc.

That's why I'd like <workunit> or <result> to give the <coproc> information, or whatever else allowing me to know which processor we run on.

J. Ph.


<app_version>
    <app_name>collatz_sieve</app_name>
    <version_num>121</version_num>
    <platform>x86_64-pc-linux-gnu</platform>
    <avg_ncpus>0.167393</avg_ncpus>
    <max_ncpus>0.167393</max_ncpus>
    <flops>2919764919751.584961</flops>
    <plan_class>opencl_amd_gpu</plan_class>
    <api_version>7.7.0</api_version>
    <file_ref>

<file_name>collatz_sieve_1.21_x86_64-pc-linux-gnu__opencl_amd_gpu</file_name>
        <main_program/>
    </file_ref>
    <file_ref>

<file_name>collatz_sieve_1.21_x86_64-pc-linux-gnu__opencl_amd_gpu.config</file_name>
        <open_name>collatz.config</open_name>
        <copy_file/>
    </file_ref>
    <coproc>
        <type>ATI</type>
        <count>1.000000</count>
    </coproc>
    <gpu_ram>48234496.000000</gpu_ram>
    <dont_throttle/>
</app_version>
<app_version>
    <app_name>collatz_sieve</app_name>
    <version_num>121</version_num>
    <platform>x86_64-pc-linux-gnu</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>1329031347187.512207</flops>
    <api_version>7.7.0</api_version>
    <file_ref>
        <file_name>collatz_sieve_1.21_x86_64-pc-linux-gnu</file_name>
        <main_program/>
    </file_ref>
    <file_ref>

<file_name>collatz_sieve_1.21_x86_64-pc-linux-gnu.config</file_name>
        <open_name>collatz.config</open_name>
        <copy_file/>
    </file_ref>
</app_version>
<workunit>
    <name>collatz_sieve_2967738579240559312896_6597069766656</name>
    <app_name>collatz_sieve</app_name>
    <version_num>121</version_num>
    <rsc_fpops_est>52167487999967232.000000</rsc_fpops_est>
    <rsc_fpops_bound>5216748799996723200.000000</rsc_fpops_bound>
    <rsc_memory_bound>100000000.000000</rsc_memory_bound>
    <rsc_disk_bound>100000000.000000</rsc_disk_bound>
    <file_ref>

<file_name>collatz_sieve_2967738579240559312896_6597069766656</file_name>
        <open_name>in.txt</open_name>
    </file_ref>
</workunit>

Le 19/11/2016 à 21:25, David Anderson a écrit :
The <app_version> element already contains this info: e.g.

<app_version>
    <app_name>setiathome_v8</app_name>
    <version_num>820</version_num>
    <platform>windows_intelx86</platform>
    <avg_ncpus>0.001776</avg_ncpus>
    <max_ncpus>0.001776</max_ncpus>
    <flops>6710859671.000872</flops>
    <plan_class>opencl_intel_gpu_sah</plan_class>
...
    <coproc>
        <type>intel_gpu</type>
        <count>1.000000</count>
    </coproc>
    <gpu_ram>264241152.000000</gpu_ram>
    <dont_throttle/>
</app_version>


On 11/19/2016 9:56 AM, Jean Philippe EIMER wrote:
Hi,

As the developper of the boinc bash script, I'd like
'client_state.xml' to give the processor workunit/result is computed
on (I mean CPU or GPU).

With <app_version>, we know the application will run on CPU or GPU.

But, some projects (collatz, milkyway) have same name and version
number for application running on CPU or on GPU, preventing the bash
script to know the processor used.

Is this modification possible ?

Thank you for your feedback.

Best regards,
J. Ph.
_______________________________________________
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