Em 07-07-2017 18:44, Brice Goglin escreveu:
Does "ldd /path/to/libhwloc.so" say that it depends on libcuda?
Check the end of the configure output, you should see "CUDA" on the
"probe/display I/O devices" line:
-
Hwloc o
27;m sure I'm doing something stupid here... I'm certainly new
> to using hwloc.
>
> Dave
>
>
>
> From:Brice Goglin
> To: Hardware locality user list
> Date:07/07/2017 02:54 PM
> Subject:Re: [hwloc-users] Why do I get such little informa
ing something stupid here... I'm certainly new to
using hwloc.
Dave
From: Brice Goglin
To: Hardware locality user list
Date: 07/07/2017 02:54 PM
Subject: Re: [hwloc-users] Why do I get such little information
back about GPU's on my system
Sent by:"hwloc-us
Le 07/07/2017 21:51, David Solt a écrit :
> Oh, Geoff Paulsen will be there at Open MPI meeting and he can help
> with the discussion. We tried searching for
>
> // Iterate over each osdevice and identify the GPU's on each socket.
> while ((obj = hwloc_get_next_osdev(machine_topology, obj)) !
t
Date: 07/07/2017 02:21 PM
Subject: Re: [hwloc-users] Why do I get such little information
back about GPU's on my system
Sent by:"hwloc-users"
Thank you so much! We are going to try this out and I'll let you know
what we find. Yes, I think we got dis
2017 02:02 PM
Subject: Re: [hwloc-users] Why do I get such little information
back about GPU's on my system
Sent by:"hwloc-users"
Le 07/07/2017 20:38, David Solt a écrit :
We are using the hwloc api to identify GPUs on our cluster. While we are
able to &
Le 07/07/2017 20:38, David Solt a écrit :
> We are using the hwloc api to identify GPUs on our cluster. While we
> are able to "discover" the GPUs, other information about them does not
> appear to be getting filled in. See below for example:
> (gdb) p *obj->attr
> $20 = {
> cache = {
> size
