GPU details are sent in scheduler request messages,
and are used to make scheduling decisions.
The details are not stored in the database.
PHP pages can see only what's in the database.
On 05-Jun-2013 2:51 PM, Jorden van der Elst wrote:
It's not stored in the database, but it is sent to the project.
<coprocs>
<coproc_ati>
<count>1</count>
<name>AMD Radeon HD 6790/6850/6870 series (Barts)</name>
<available_ram>2112880640.000000</available_ram>
<have_cal>1</have_cal>
<have_opencl>1</have_opencl>
<req_secs>0.000000</req_secs>
<req_instances>0.000000</req_instances>
<estimated_delay>0.000000</estimated_delay>
<peak_flops>2976000000000.000000</peak_flops>
<CALVersion>1.4.1741</CALVersion>
<target>17</target>
<localRAM>2048</localRAM>
<uncachedRemoteRAM>2047</uncachedRemoteRAM>
<cachedRemoteRAM>2047</cachedRemoteRAM>
<engineClock>775</engineClock>
<memoryClock>1000</memoryClock>
<wavefrontSize>64</wavefrontSize>
<numberOfSIMD>12</numberOfSIMD>
<doublePrecision>0</doublePrecision>
<pitch_alignment>256</pitch_alignment>
<surface_alignment>4096</surface_alignment>
<maxResource1DWidth>16384</maxResource1DWidth>
<maxResource2DWidth>16384</maxResource2DWidth>
<maxResource2DHeight>16384</maxResource2DHeight>
<atirt_detected/>
<coproc_opencl>
<name>AMD Radeon HD 6790/6850/6870 series (Barts)</name>
<vendor>Advanced Micro Devices, Inc.</vendor>
<vendor_id>4098</vendor_id>
<available>1</available>
<half_fp_config>0</half_fp_config>
<single_fp_config>62</single_fp_config>
<double_fp_config>0</double_fp_config>
<endian_little>1</endian_little>
<execution_capabilities>1</execution_capabilities>
<extensions>cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics
cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes
cl_khr_byte_addressable_store cl_khr_gl_sharing
cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3
cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt
cl_khr_d3d10_sharing </extensions>
<global_mem_size>2147483648</global_mem_size>
<local_mem_size>32768</local_mem_size>
<max_clock_frequency>775</max_clock_frequency>
<max_compute_units>12</max_compute_units>
<opencl_platform_version>OpenCL 1.2 AMD-APP
(1124.2)</opencl_platform_version>
<opencl_device_version>OpenCL 1.2 AMD-APP
(1124.2)</opencl_device_version>
<opencl_driver_version>1124.2 (VM)</opencl_driver_version>
</coproc_opencl>
</coproc_ati>
</coprocs>
That's from my sched_request_einstein.phys.uwm.edu.xml file. Why do we
send all that info in if most of it isn't used or stored anywhere?
So why do we still predominantly show the CAL version number, and not
the OpenCL number that's being used?
And if that needs to be for multiple GPUs, the info can go on a
separate page, just as the application details.
Now we're constantly asking people who post on the forums for help to
post their messages to see if the GPU's OpenCL capability was even
detected. If we could check that from their computers, it would make
our lives easier.
As always, not in a hurry about it. Just a feature request for the to
do list? :-)
On Wed, Jun 5, 2013 at 6:18 AM, David Anderson <[email protected]> wrote:
Not currently; OpenCL info is not stored in the database.
-- David
On 04-Jun-2013 9:35 AM, Jorden van der Elst wrote:
Can we get the OpenCL details of the detected GPU(s) in project's user
account->computer details as well, please? Or only that line when it
comes to AMD/ATI GPUs? At present we're showing only the CAL line,
while in most project's cases we need the information in the OpenCL
line. If it's detected at least. Therefore also when it's not
detected, state that it's not detected?
With thanks,
--
-- Jord van der Elst.
--
-- Jord van der Elst.
_______________________________________________
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.
--
-- Jord van der Elst.
_______________________________________________
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.
