Le 30/11/2011 08:44, Stefan Eilemann a écrit :
> Let me know if I can help. We would be quite interested in this feature.
You can help by asking the relevant people for help :)
* ask the OpenCL board to add an device query property that tells us the
locality of a device. If they return the BusID o
On 29. Nov 2011, at 11:36, Brice Goglin wrote:
> Le 29/11/2011 09:57, Stefan Eilemann a écrit :
>>
>> I use them mostly with OpenGL ('XOpenDisplay(":0.")' and RDMA in
>> Equalizer/Collage (see links in signature). Is there a straight way to
>> associate the GPUs with the corresponding X screen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/11/11 03:24, Guy Streeter wrote:
> There is a request pending to have hwloc updated to 1.3 in
> RHEL6. I do not yet have a schedule for it.
I wouldn't hold your breath, I'm still waiting for a nasty
kernel bug to be fixed in RHEL5 (ethernet pac
On Nov 29, 2011, at 1:04 PM, Brice Goglin wrote:
> "XML output" should be "XML input/output" or "XML support".
Done:
-
Hwloc optional build support status (more details can be found above):
Probe / display PCI devices:
> Hwloc optional build support status (more details can be found above):
>
> Probe / display PCI devices: yes
> Graphical output (Cairo):yes
> XML output: full
"XML output" should be "XML input/output" or "XML support".
> Memory support: binding, set policy, mig
On Nov 29, 2011, at 12:01 PM, Brice Goglin wrote:
> Yes, always installed. There are some configure checks for verbs, but
> it's only used for enabling verbs-related helper testing.
Ok, how's this for output at the end of configure?
Linux:
--
Le 29/11/2011 17:58, Jeff Squyres a écrit :
> On Nov 29, 2011, at 11:53 AM, Brice Goglin wrote:
>
>>> What about MX, verbs, Cuda, ...?
>> MX and verbs are not used internally, we just have public helpers to
>> interoperate with them (and tests).
> I forget -- are the helpers installed/available eve
On Nov 29, 2011, at 11:53 AM, Brice Goglin wrote:
>> What about MX, verbs, Cuda, ...?
>
> MX and verbs are not used internally, we just have public helpers to
> interoperate with them (and tests).
I forget -- are the helpers installed/available even if the MX
headers/libraries are not found at
Le 29/11/2011 17:50, Jeff Squyres a écrit :
> On Nov 29, 2011, at 10:33 AM, Brice Goglin wrote:
>
>>> - Kerrighard
>>> - PCI device support
>>> - XML support
>> I would put XML, PCI, Cairo and libnuma
> What about MX, verbs, Cuda, ...?
MX and verbs are not used internally, we just have public help
On Nov 29, 2011, at 10:33 AM, Brice Goglin wrote:
>> - Kerrighard
>> - PCI device support
>> - XML support
>
> I would put XML, PCI, Cairo and libnuma
What about MX, verbs, Cuda, ...?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing
On 11/29/2011 02:57 AM, Stefan Eilemann wrote:
> Bonjour Brice,
>
> On 29. Nov 2011, at 9:45, Brice Goglin wrote:
>
>> hwloc 1.3 already has support for PCI device detection. These new
>> objects contain a "class" field that can help you know if it's a NIC/GPU/...
>
> Ok, time to upgrade my inst
On 11/29/2011 06:25 AM, Stefan Eilemann wrote:
>
> On 29. Nov 2011, at 11:41, Samuel Thibault wrote:
>
>> You are probably missing the libpci-devel package.
>
> Thanks, that either doesn't exist or wasn't installed on Redhat. It works now.
>
> I think messages of found/not found optional module
Le 29/11/2011 16:19, Jeff Squyres a écrit :
> On Nov 29, 2011, at 10:16 AM, Stefan Eilemann wrote:
>
>>> FWIW, I've traditionally been against such things for two reasons:
>> Your call, really. The information is there and not too hard to find, but I
>> missed it on the first run. Most software I
On Nov 29, 2011, at 10:16 AM, Stefan Eilemann wrote:
>> FWIW, I've traditionally been against such things for two reasons:
>
> Your call, really. The information is there and not too hard to find, but I
> missed it on the first run. Most software I know provides this in a very
> concise list at
Hi Jeff,
On 29. Nov 2011, at 15:28, Jeff Squyres wrote:
>> I think messages of found/not found optional modules could be more prominent
>> at the end of the configure process.
>
> FWIW, I've traditionally been against such things for two reasons:
Your call, really. The information is there and
On Nov 29, 2011, at 7:25 AM, Stefan Eilemann wrote:
>> You are probably missing the libpci-devel package.
>
> Thanks, that either doesn't exist or wasn't installed on Redhat. It works now.
>
> I think messages of found/not found optional modules could be more prominent
> at the end of the confi
On 29. Nov 2011, at 11:41, Samuel Thibault wrote:
> You are probably missing the libpci-devel package.
Thanks, that either doesn't exist or wasn't installed on Redhat. It works now.
I think messages of found/not found optional modules could be more prominent at
the end of the configure process
Stefan Eilemann, le Tue 29 Nov 2011 11:40:18 +0100, a écrit :
> Maybe I'm missing something, but I don't see any PCI-related output with
> lstopo.
You are probably missing the libpci-devel package.
Samuel
Hi Brice,
On 29. Nov 2011, at 9:45, Brice Goglin wrote:
> hwloc 1.3 already has support for PCI device detection. These new
> objects contain a "class" field that can help you know if it's a NIC/GPU/...
>
> Just run lstopo
> on your machine to see what I am talking about.
Maybe I'm missing some
Le 29/11/2011 09:57, Stefan Eilemann a écrit :
>
> I use them mostly with OpenGL ('XOpenDisplay(":0.")' and RDMA in
> Equalizer/Collage (see links in signature). Is there a straight way to
> associate the GPUs with the corresponding X screen? I guess at least the path
> through the Xorg PCI ID s
Bonjour Brice,
On 29. Nov 2011, at 9:45, Brice Goglin wrote:
> hwloc 1.3 already has support for PCI device detection. These new
> objects contain a "class" field that can help you know if it's a NIC/GPU/...
Ok, time to upgrade my installation. The cluster has RHEL6.1 which ships with
an older
Hello Stefan,
hwloc 1.3 already has support for PCI device detection. These new
objects contain a "class" field that can help you know if it's a NIC/GPU/...
However it's hard to know which PCI device is eth0 or eth1, so we also
try to add some OS device inside PCI device. If you're using Linux, y
22 matches
Mail list logo
