[hwloc-devel] Create success (hwloc r1.1a1r2291)

2010-07-07 Thread MPI Team
Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.1a1r2291 Start time: Wed Jul 7 21:01:02 EDT 2010 End time: Wed Jul 7 21:03:06 EDT 2010 Your friendly daemon, Cyrador

Re: [hwloc-devel] Ad

2010-07-07 Thread Jirka Hladky
(Forgot to CC the list) Hi Brice, On Wednesday, July 07, 2010 04:16:19 pm Brice Goglin wrote: > Le 07/07/2010 13:40, Jirka Hladky a écrit : > > Well, I would expect to get following reported on STDERR (refer to lstopo > > output) when -v is specified: > > > > ./hwloc-calc -v --list 4 proc:60 > >

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Brice Goglin
Le 07/07/2010 13:48, Jirka Hladky a écrit : > I know that such mapping is artificial. However, it enables me to see that > hyper threading is enabled. I use it in my reports only. > Just compare the number of cores and the number of PUs. It should be enough to know if each core has multiple th

[hwloc-devel] Fwd: Ad

2010-07-07 Thread Brice Goglin
(Forgot to CC the list) Le 07/07/2010 13:40, Jirka Hladky a écrit : > Well, I would expect to get following reported on STDERR (refer to lstopo > output) when -v is specified: > > ./hwloc-calc -v --list 4 proc:60 > L2 #30 (256KB) > > ./hwloc-calc -v --list 5 proc:60 > L1 #30 (3

Re: [hwloc-devel] hwloc-distrib: how to start at lower hiearchy level?

2010-07-07 Thread Jirka Hladky
On Monday, July 05, 2010 07:12:58 am Brice Goglin wrote: > Le 05/07/2010 02:41, Jirka Hladky a écrit : > > Hi all, > > > > I'm using hwloc-distrib quite often to distribute jobs optimally on NUMA > > boxes. I use it to test linux kernel task - scheduler by comparing > > runtime of jobs bound to be

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Jirka Hladky
Hi Brice, update to my post regarding --list option: > > I have downloaded hwloc-1.1a1r2290.tar.bz2 > > > r.bz2>but apparently the modification is not there yet. If I get right > > you have implemented following, right? >

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Jirka Hladky
Hi Brice, I have one question regarding thread id: === ./hwloc-calc --physical --list core proc:60 11 is matching with core id : 11 from /proc/cpuinfo ./hwloc-calc --physical --list socket proc:60 0 is matching with physical id : 0 from /proc/cpuin

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Brice Goglin
Le 07/07/2010 12:37, Jirka Hladky a écrit : > I have also tested depth argument for --list. (BTW, what has happened with > hwloc-info? I cannot find it anymore. Is there some replacement?) > It's a symlink that we create during make install. It doesn't exist in the build directory. Did you mak

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Jirka Hladky
Hi Brice, I have tested the patch and I have verified that === ./hwloc-calc --list numanode proc:32 ./hwloc-calc --list socket proc:63 ./hwloc-calc --list core proc:63 === is working as expected. Thanks a lot! I have also tested de

Re: [hwloc-devel] hwloc-distrib: how to start at lower hiearchy level?

2010-07-07 Thread Jirka Hladky
Hi Brice, > > The box has strange NUMA layout - I will need to check why it is so. > > Basically, there are 3 NUMA nodes - one includes 2 Sockets, other 2 have > > one Socket associated to each of it. > > Seems strange to me, likely a BIOS bug. Nehalem-EX should always have > one NUMA node per so

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Brice Goglin
Le 07/07/2010 11:15, Jirka Hladky a écrit : > I have also seen you recent change: > > == > > --list > > and replaces > > --nodelist with --list numanode (still supported but undocumented) > > It should work for core and socket as well. > > == > > I h

Re: [hwloc-devel] How to get information about hwloc objects?

2010-07-07 Thread Jirka Hladky
On Monday, July 05, 2010 07:04:22 am Brice Goglin wrote: > Le 05/07/2010 02:06, Jirka Hladky a écrit : > > I need to get NUMAnode since I'm comparing numactl and taskset commands. > > --pulist and --nodelist were designed for when you need to pass the > result to numactl > I'm already using thes