Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] python bindings testing help needed
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2013-06-05 01:29:55


Le 05/06/2013 00:03, Guy Streeter a écrit :
> On 06/04/2013 03:52 AM, Brice Goglin wrote:
>> (forgot to CC the list)
>>
>>
>> Le 04/06/2013 10:48, Brice Goglin a écrit :
>>> Hello,
>>>
>>> Here are some slightly fixed tests. cuda/cudart/nvml look good.
>>> intel-mic looks good but I couldn't test on a real machine (I used XML
>>> instead), so the cpuset retrieving code wasn't tested.
>>>
>>> gl doesn't seem to find any GPU, but I don't know enough about Python to
>>> debug things. If you have a debugging version, I can test it.
>>>
> I think my regular expression code is broken in the gl stuff. Do you have to
> have the hardware and drivers for GL, or could I use an XML file for testing?
>
> The main thing I need to know is what the "name" of a GPU object really looks
> like. Perhaps the output of the hwloc gl test on an appropriate system would help.
>

Here's a XML with cuda/nvml/gl objects. Just set HWLOC_XMLFILE to this
file in your environment. Note that most functions get_foo_cpuset()
won't work in this case (since they directly read cpuset from Linux
sysfs files).

And the output of the tests are below.

Brice

$ ./cuda
cuDeviceGetCount found 3 devices
found OSDev cuda0
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 0
found OSDev cuda1
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 1
found OSDev cuda2
found OSDev model Tesla C2050
got cpuset 0x00fc0fc0 for device 2

$ ./cudart
cudaGetDeviceCount found 3 devices
found OSDev cuda0
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 0
found OSDev cuda1
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 1
found OSDev cuda2
found OSDev model Tesla C2050
got cpuset 0x00fc0fc0 for device 2

$ ./gl
 0x0003f03f | NVIDIA Corporation GF100 [Tesla C2050 / C2070]
 0x0003f03f | NVIDIA Corporation GF100 [Tesla C2050 / C2070]
 0x0003f03f | Intel Corporation 82574L Gigabit Network Connection
 0x0003f03f | Intel Corporation 82574L Gigabit Network Connection
 0x0003f03f | Matrox Electronics Systems Ltd. MGA G200eW WPCM450
 0x0003f03f | Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
 0x00fc0fc0 | NVIDIA Corporation GF100 [Tesla C2050 / C2070]
GPU #0 (Tesla C2050) is connected to DISPLAY:0.0
GPU #1 (Tesla C2050) is connected to DISPLAY:0.3
GPU #2 (Tesla C2050) is connected to DISPLAY:0.2
GPU :0.0 (PCI 0000:02:00.0) is connected to DISPLAY:0.0 close to 0x0003f03f
GPU :0.2 (PCI 0000:84:00.0) is connected to DISPLAY:0.2 close to 0x00fc0fc0

$ ./nvml
nvmlDeviceGetCount found 3 devices
found OSDev nvml0
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 0
found OSDev nvml1
found OSDev model Tesla C2050
got cpuset 0x0003f03f for device 1
found OSDev nvml2
found OSDev model Tesla C2050
got cpuset 0x00fc0fc0 for device 2