Re: [hwloc-users] lstopo and GPus

Just another things: The id showed in the GPU box from lstopo, is the same device_id CUDA numeration used in some function like setDevice() for example? More better: gpu 1 from lstopo = ? gpu 1 for CUDA runtime? Thanks. 2012/8/29 Gabriele Fatigati > Good! > > Now it

Re: [hwloc-users] lstopo and GPus

Good! Now it works well. Many tanks! 2012/8/28 Samuel Thibault > Gabriele Fatigati, le Tue 28 Aug 2012 18:10:41 +0200, a écrit : > > How can cuda branch help me? lstopo output of that branch is the same of > the > > trunk. > > You need to make sure that hwloc found

Re: [hwloc-users] lstopo and GPus

Hi, thanks for the reply. How can cuda branch help me? lstopo output of that branch is the same of the trunk. Another question: the GPU IDs are the same (10de: 06d2). How is it possible? Thanks. 2012/8/28 Samuel Thibault > Brice Goglin, le Tue 28 Aug 2012 14:43:53

Re: [hwloc-users] lstopo and GPus

Brice Goglin, le Tue 28 Aug 2012 14:43:53 +0200, a écrit : > > $ lstopo > > Socket #0 > > Socket #1 > > PCI... > > (connected to socket #1) > > > > vs > > > > $ lstopo > > Socket #0 > > Socket #1 > > PCI... > > (connected to both sockets) > > Fortunately, this won't occur in most

Re: [hwloc-users] lstopo and GPus

Le 28/08/2012 14:23, Samuel Thibault a écrit : > Gabriele Fatigati, le Tue 28 Aug 2012 14:19:44 +0200, a écrit : >> I'm using hwloc 1.5. I would to see how GPUs are connected with the processor >> socket using lstopo command. > About connexion with the socket, there is indeed no real graphical >

Re: [hwloc-users] lstopo and GPus

Gabriele Fatigati, le Tue 28 Aug 2012 14:19:44 +0200, a écrit : > I'm using hwloc 1.5. I would to see how GPUs are connected with the processor > socket using lstopo command.  About connexion with the socket, there is indeed no real graphical difference between "connected to socket #1" and