Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and confusion

2012-08-07 Thread Brice Goglin
On Behalf Of Brice Goglin > Sent: Monday, August 06, 2012 4:47 PM > To: Wheeler, Kyle Bruce > Cc: > Subject: Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and > confusion > > Le 07/08/2012 00:36, Wheeler, Kyle Bruce a écrit : >> A, that's key! The d

Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and confusion

2012-08-06 Thread Kenneth A. Lloyd
August 06, 2012 4:47 PM To: Wheeler, Kyle Bruce Cc: Subject: Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and confusion Le 07/08/2012 00:36, Wheeler, Kyle Bruce a écrit : > A, that's key! The documentation currently says "Look at ancestor > objects from the b

Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and confusion

2012-08-06 Thread Brice Goglin
Le 07/08/2012 00:36, Wheeler, Kyle Bruce a écrit : > A, that's key! The documentation currently says "Look at ancestor > objects from the bottom to the top until one of them contains a > distance matrix that matches the objects exactly", which suggests to > me that it will traverse the object h

Re: [hwloc-users] [EXTERNAL] Re: hwloc_get_latency() failures and confusion

2012-08-06 Thread Wheeler, Kyle Bruce
On Aug 6, 2012, at 4:08 PM, Brice Goglin wrote: > You should not be getting a distance matrix for depth 0 above. You get > one for depth=1 (the depth of NUMAnodes in your topology). Ahh, ok. Well, at least I know what I *should* get now. :) Sheepishly, I have to admit that I just figured it out