Re: [hwloc-devel] Negative values for die_id and physical_package_id

PU P#4 PU P#6 L2 (1024KB) + L1d (32KB) + L1i (48KB) PU P#1 PU P#3 PU P#5 PU P#7 Group0 NUMANode P#3 (5354MB) Block(Disk) "sda" Net "env2" On Wed, May 26, 2021 at 2:33 PM Brice Goglin wrote: > Le 26/05/202

Re: [hwloc-devel] Negative values for die_id and physical_package_id

only, to print 4294967295 as -1? Thanks! Jirka On Wed, May 26, 2021 at 2:14 PM Brice Goglin wrote: > Le 26/05/2021 à 13:51, Jirka Hladky a écrit : > > Hi Brice, > > I would like to get your opinion on the following issue. On IBM LPAR, > kernel reports die_id and physical_pac

[hwloc-devel] Negative values for die_id and physical_package_id

Hi Brice, I would like to get your opinion on the following issue. On IBM LPAR, kernel reports die_id and physical_package_id to be -1. See [0] hwloc-calc converts these values into an unsigned integer, resulting in Socket ID 2^32-1: hwloc-calc --physical-output --intersect socket core:0

Re: [hwloc-devel] hwloc on IBM Power LPAR VMs

eed to > support node0 being offline as well. > It's not clear whether it's a new Linux feature or not, > this was reported on a POWER LPAR VM. > > We opportunistically assume node0 is online to avoid > the overhead in the vast majority of cases. If node0 > is missing, we parse "

[hwloc-devel] hwloc on IBM Power LPAR VMs

Hi Brice, how are you doing? I hope you are fine. We are all well and safe. I have been running hwloc on IBM Power LPAR VM with only 1 CPU core and 8 PUs [1]. There is only one NUMA node. The numbering is however quite strange, the NUMA node number is "2". See [2]. hwloc reports "Topology does

Re: [hwloc-devel] Strange CPU topology numbering on dual socket ARM server with 2×ThunderX2 CN9975

> > Yes, that is why hwloc provides both, and hwloc-calc can be used to > convert between them for instance. Exactly! I use hwloc-calc quite heavily to connect both worlds. On Fri, Sep 6, 2019 at 5:21 PM Samuel Thibault wrote: > Jirka Hladky, le ven. 06 sept. 2019 16:52:30 +0

Re: [hwloc-devel] Strange CPU topology numbering on dual socket ARM server with 2×ThunderX2 CN9975

; > Hi, > > You should avoid physical numbering at any cost. > > Guillaume > > On 9/6/19 4:38 PM, Jirka Hladky wrote: > > Thanks for the feedback! I have never seen anything like that so I have > > assumed it's a bug:-) > > > > I was already thinking ab

Re: [hwloc-devel] Strange CPU topology numbering on dual socket ARM server with 2×ThunderX2 CN9975

Thanks for the feedback! I have never seen anything like that so I have assumed it's a bug:-) I was already thinking about using the logical numbering - it's probably the best solution. Merci beaucoup! Jirka On Fri, Sep 6, 2019 at 4:13 PM Samuel Thibault wrote: > Brice Goglin, le ven. 06

Re: [hwloc-devel] python-hwloc available via pip install

DME.rst > thanks, > --Guy > > On Wed, Jan 3, 2018 at 4:15 PM Jirka Hladky <jhla...@redhat.com> wrote: > >> Hi Guy, >> >> please note that the examples are not visible in the rendered file (the >> default view). Please check the attached snapshot. >> &

Re: [hwloc-devel] python-hwloc available via pip install

Hi Guy, please note that the examples are not visible in the rendered file (the default view). Please check the attached snapshot. Thanks a lot! Jirka On Wed, Jan 3, 2018 at 11:03 PM, Guy Streeter wrote: > I've made python-hwloc available to install through pip. It's a

Re: [hwloc-devel] Static analysis

NULL then. > > > > Thanks, > > Lukas > > > > *From:* hwloc-devel [mailto:hwloc-devel-boun...@open-mpi.org] *On Behalf > Of *Jirka Hladky > *Sent:* Tuesday, January 12, 2016 3:01 PM > *To:* Hardware locality development list > > *Subject:* Re: [hwloc

Re: [hwloc-devel] Static analysis

Hi Brice, I use following custom routines to check for malloc related errors. Just my 2 cents. Jirka void *util_Malloc (size_t size) { void *p; errno = 0; p = malloc (size); if (p == NULL) { fprintf (stdout, "\nmalloc failed: %s\n\n", strerror (errno)); exit

Re: [hwloc-devel] hwloc to be included in RHEL 6.1

On Monday, November 22, 2010 11:24:19 pm Samuel Thibault wrote: > Jeff Squyres, le Mon 22 Nov 2010 21:54:04 +0100, a écrit : > > Better yet -- include a legend/text explanation line (or even just a > > title, "Physical|Logical numbering of processors in [hostname] at > > [time/date]") > > That,

Re: [hwloc-devel] ***UNCHECKED*** [WARNING: A/V UNSCANNABLE]Re: hwloc-distrib --among

On Monday, November 22, 2010 07:00:56 pm Samuel Thibault wrote: > Jirka Hladky, le Mon 22 Nov 2010 18:54:24 +0100, a écrit : > > However, I was wondering if there is some way to get the old way, i.e to > > distribute the jobs among NUMA nodes. I DO NOT use this mode but I don't &

Re: [hwloc-devel] ***UNCHECKED*** [WARNING: A/V UNSCANNABLE]Re: hwloc-distrib --among

On Monday, November 22, 2010 02:08:50 pm Samuel Thibault wrote: > Hello, > > Jirka Hladky, le Thu 18 Nov 2010 15:14:07 +0100, a écrit : > > My goal is to distribute one job per Socket with command > > hwloc-distrib --single 8 > > Could you try again with the current

Re: [hwloc-devel] hwloc to be included in RHEL 6.1

On Monday, November 22, 2010 05:57:34 pm Samuel Thibault wrote: > Samuel Thibault, le Mon 22 Nov 2010 17:33:15 +0100, a écrit : > > > -- using "p" is a good way to indicate "physical". But IIRC, we didn't > > > like "l" (for "logical") because it looks too much like 1 (one). > > > > > > I think

Re: [hwloc-devel] hwloc to be included in RHEL 6.1

On Thursday, November 18, 2010 03:55:35 pm Brice Goglin wrote: > Le 18/11/2010 08:50, Jirka Hladky a écrit : > > Hi all, > > > > Red Hat would like to included hwloc in the upcoming version of the Red > > Hat Enterprise Linux 6.1. There is Bugzilla 648593 > >

Re: [hwloc-devel] hwloc-distrib --among

Hi Samuel, thanks for looking into it! I'm using hwloc_distribute to distribute parallel jobs on multi-socket systems. Usually, it gives nice results: running hwloc-distrib --single on box with sockets will ditrbitute one job per socket. This is what I want. hwloc-distrib --single <2*N>

Re: [hwloc-devel] hwloc-distrib --among

On Tuesday, November 16, 2010 10:31:11 pm Brice Goglin wrote: > Le 16/11/2010 15:18, Samuel Thibault a écrit : > > Jirka Hladky, le Tue 16 Nov 2010 21:37:01 +0100, a écrit : > >> There was some discussion about hwloc-distrib --among > >> > >> If I understa

[hwloc-devel] hwloc-distrib --among

Hi Brice, I had hold an internal presentation on hwloc. It was success, people has liked it. One colleague has tried it on 8 socket box and we have found that memory was installed in the wrong slots resulting in very strange NUMA configuration. There was some discussion about hwloc-distrib

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

On Thursday, November 11, 2010 07:19:41 pm Samuel Thibault wrote: > Jirka Hladky, le Thu 11 Nov 2010 14:50:46 +0100, a écrit : > > "On this system function XYZ is not supported by GLIBC/KERNEL)" > > > > I'm missing the information: > > > > -which func

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

On Thursday, November 11, 2010 01:43:38 pm Samuel Thibault wrote: > Jirka Hladky, le Thu 11 Nov 2010 13:36:46 +0100, a écrit : > > > hwloc_get_membind failed (errno 38 Function not implemented) > > > > Yes, you are right! > > --get --pid > > works on L

Re: [hwloc-devel] hwloc-1.2a1r2694 and hwloc-1.2a1r2751

0, 2010 07:33:19 pm Brice Goglin wrote: > I don't see any change in this test between 2694 and 2751. Do you get a > better backtrace if you compile in debug mode (and/or with CFLAGS="-g > -O0") or with gdb? > > Brice > > Le 10/11/2010 15:56, Jirka Hladky a écrit : > &

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

Hi Brice, hi Samuel, see my comments bellow. > > 1) Does the option --get works together with --pid ? Like finding out > > mempolicy for any pid? I don't think that get_mempolicy supports this. > > hwloc indeed gives: > > hwloc_get_membind failed (errno 38 Function not implemented) Yes, you

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

On Thursday, November 11, 2010 11:11:31 am Brice Goglin wrote: > Le 11/11/2010 02:31, Samuel Thibault a écrit : > >> get_mempolicy: Invalid argument > >> hwloc_get_membind failed (errno 22 Invalid argument) > > > > Could you try to increase the value of max_os_index? > > > > I can see in the

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

HI Brice, On Wednesday, November 10, 2010 02:28:46 pm Brice Goglin wrote: > Le 10/11/2010 14:09, Jirka Hladky a écrit : > > Hi Brice, > > > > I have found couple of issues with 1.1rc2 > > > > 1) man hwloc-bind > > Following example does not work: > &

[hwloc-devel] hwloc-1.1rc2

Hi Brice, I have problems with make check on RHEL 6.0 for hwloc-1.1rc2 Please see attached log file. I have installed numactl-devel package before compiling hwloc. Anything else is needed with respect to NUMA? Thanks! Jirka Making check in src make[1]: Entering directory

Re: [hwloc-devel] [hwloc-announce] Hardware locality (hwloc) v1.1rc1 released

Hi Brice, I have found couple of issues with 1.1rc2 1) man hwloc-bind Following example does not work: $ hwloc-bind --cpubind node:1 --membind:0 echo hello Unrecognized option: --membind:0 2) hwloc-bind --get --membind is not working for me (RHEL 6.0) $ hwloc-bind --membind node:1 --mempolicy

Re: [hwloc-devel] Strange results on itanium 2

On Sunday, October 31, 2010 09:45:04 am Brice Goglin wrote: > Le 30/10/2010 00:55, Jirka Hladky a écrit : > > > >> L2 and one L1 per core. Your machine has hyperthreading, so our > > > >> > > > >> This work-around worked fine on old itaniums since

[hwloc-devel] gather-topology.sh and rpm

Hi all, since gather-topology.sh is nice script to help debug problems I was thinking to add it to the rpm. However, path to the lstopo is set to the absolute build path: abs_top_builddir="/home/jhladky/tests/performance/hwloc/hwloc-1.0.2" lstopo="$abs_top_builddir/utils/lstopo" so it will no

Re: [hwloc-devel] Strange results on itanium 2

On Saturday, October 30, 2010 12:24:14 am Brice Goglin wrote: > Le 30/10/2010 00:01, Jirka Hladky a écrit : > > On Friday, October 29, 2010 10:59:25 pm Brice Goglin wrote: > >> Le 29/10/2010 21:57, Jirka Hladky a écrit : > >>> Hi Samuel, > >>> > >&g

Re: [hwloc-devel] Strange results on itanium 2

On Friday, October 29, 2010 10:59:25 pm Brice Goglin wrote: > Le 29/10/2010 21:57, Jirka Hladky a écrit : > > Hi Samuel, > > > > I have attached the output of > > tests/linux/gather-topology.sh `uname --kernel-release`_`uname -- > > nodename`_gather-topology >

Re: [hwloc-devel] Strange results on itanium 2

is not supported on RHEL 6.0 so I cannot really test it on the new kernel. It would be really interesting if you can recognize if it's a kernel bug or hwloc problem. Thanks a lot! Jirka On Wednesday, October 27, 2010 02:59:30 pm Samuel Thibault wrote: > Hello, > > Jirka Hladky, le W

[hwloc-devel] Strange results on itanium 2

Hi all, I have run hwloc on system with 2 itanium 2 cpus. Results are not OK, L3 cache is bellow L2 cache. Could you please check it? BOX: HP Integrity BL870c Output of command: "lstopo --physical -" Machine (16GB) Socket p#0 L2 (256KB) + L1 (16KB) + Core p#0 L3 (9216KB) + PU p#0

Re: [hwloc-devel] hwloc on power7

gt; as we always have. > > Signed-off-by: Anton Blanchard <an...@samba.org> > Signed-off-by: Benjamin Herrenschmidt <b...@kernel.crashing.org> > > > Maybe some distros should backport it... > > Brice > > Le 05/08/2010 00:19, Jirka Hladky a écrit : > &

Re: [hwloc-devel] hwloc on power7

I have just found that cat /sys/devices/system/cpu/cpu*/topology/physical_package_id -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 which seems to be wrong. Jirka On Thursday, August 05, 2010 12:19:41 am Jirka Hladky wrote: > Hi, > &g

[hwloc-devel] hwloc on power7

Hi, I just got access to one POWER7 box. Both hwloc 1.0.2 and latest hwloc 1.1 seem to have problems to detect the sockets correctly. It's IBM 8406-71Y server equipped with only one socket. On the chip there are 8 cores. lstopo seems to be wrong here, reporting 8 sockets. I'm not sure if this

Re: [hwloc-devel] hwloc is now available as package for Fedora

On Monday, August 02, 2010 11:39:55 am Brice Goglin wrote: > Le 02/08/2010 10:39, Jirka Hladky a écrit : > > Hi guys, > > > > hwloc is now available as rpm package for Fedora 12, 13 and 14. > > > > ===

Re: [hwloc-devel] How to create a patch file?

Hi Jeff, hi Brice, I just came back from vacation. Thanks a lot for creating 1.0.2 release candidate! I will update rpm and test it. Thanks! Jirka > Oops -- I see that we only have trunk nightly tarballs (oops!). I'll add > 1.0 nightly tarballs... done: > >

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

Hi Brice, > I don't like long names like that :) I currently vote for --intersect > here since this option list the indexes of all objects that intersect > the input within the given depth or type. I don't mind long descriptive names. I'm copying options usually from man page or ./command --help

Re: [hwloc-devel] How to create a patch file?

On Monday, July 12, 2010 11:27:56 pm you wrote: > Le 12/07/2010 23:17, Jirka Hladky a écrit : > > Hi Brice, > > > > thanks for backporting patch to the 1.0 branch: > > > > --- Comment #16 from Brice Goglin <brice.gog...@inria.fr> 2010-07-12 > >

Re: [hwloc-devel] hwloc on PPC64

On Sunday, July 11, 2010 07:57:48 pm Brice Goglin wrote: > Le 11/07/2010 19:48, Jirka Hladky a écrit : > > Hi all, > > > > I have run into two bugs on PPC64 on 2.6.32 kernel. > > > > Version: > > > > lt-lstopo 1.0.1 > > > > BUG #1:

[hwloc-devel] hwloc on PPC64

Hi all, I have run into two bugs on PPC64 on 2.6.32 kernel. Version: lt-lstopo 1.0.1 BUG #1: No Socket information in lstopo output: ./lstopo Machine (3654MB) + L2 #0 (4096KB) L1 #0 (64KB) + Core #0 PU #0 (phys=0) PU #1 (phys=1) L1 #1 (64KB) + Core #1 PU #2 (phys=2) PU #3

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

On Wednesday, July 07, 2010 04:56:54 pm Brice Goglin wrote: > 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

Re: [hwloc-devel] Ad

(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: > > > > ./hwl

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

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?

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

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

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 >

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

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 best possible CPU configuration (keeping CPU cache in mind) with runs without CPU affinity set. I just run into strange

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

Hi Brice, > > > > GREPLINES=$(lstopo --physical --cpuset - | wc -l) > > lstopo --physical --cpuset - | grep -B${GREPLINES} "PU p#1\b" | grep Core > > | tail -1 > > sed should reduce this dramatically, for instance with: > lstopo --physical --cpuset - | sed -n -e '0,/PU p#1/p' | grep Core | >

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

Hi folks, I need to get information about hwloc objects, particularly processor. I would love to get NUMANode number Socket number Core number for given processor. Currently, I'm parsing lstopo output but it's awkward: GREPLINES=$(lstopo --physical --cpuset - | wc -l) lstopo --physical

Re: [hwloc-devel] [hwloc-users] hwloc and rpath

On Tuesday, June 22, 2010 02:59:58 pm Jeff Squyres wrote: > On Jun 22, 2010, at 8:48 AM, Jirka Hladky wrote: > > So basically, until libtool patch will make through upstream into other > > distributions it will be needed to patch configure script. > > Bummer. But at least it

Re: [hwloc-devel] [hwloc-users] hwloc and rpath

On Tuesday, June 22, 2010 01:26:23 am Samuel Thibault wrote: > Hello, > > Jirka Hladky, le Mon 21 Jun 2010 18:54:47 +0200, a écrit : > > I don't have "/usr/lib64" directory listed in > > /etc/ld.so.conf. However, "/usr/lib64" is considered to be the

[hwloc-devel] hwloc is failing for Pentium D

Hi guys, I have been always impressed how well hwloc works. Now it seems like I have found a bug on Pentium D, but it might be bug in linux kernel as well. http://en.wikipedia.org/wiki/List_of_Intel_Pentium_D_microprocessors I have reproduced the bug on Pentium D 820 (at Dell's PowerEdge

[hwloc-devel] hwloc will be soon available as package in Fedora

%{name}-%{version} %{_defaultdocdir}/%{name}-%{version}/*c %changelog * Fri Jun 18 2010 Jirka Hladky <jhla...@redhat.com> - 1.0.1-17 - Initial build

Re: [hwloc-devel] [hwloc-users] hwloc and rpath

On Monday, June 21, 2010 09:58:08 pm Jeff Squyres wrote: > On Jun 21, 2010, at 3:18 PM, Jirka Hladky wrote: > > $chrpath --list /usr/local/bin/lstopo > > /usr/local/bin/lstopo: RPATH=/usr/local/lib > > Ah, I understand now. And I'm seeing the same behavior: > > $ cd

Re: [hwloc-devel] [hwloc-users] hwloc and rpath

On Monday, June 21, 2010 09:07:35 pm Jeff Squyres wrote: > On Jun 21, 2010, at 12:54 PM, Jirka Hladky wrote: > > However, libtool does not look into /usr/lib64 by default. I have found 2 > > ways > > > how to fix it: > Are we installing to /usr/lib64 by default

Re: [hwloc-devel] [hwloc-users] hwloc and rpath

On Monday, June 21, 2010 04:51:09 pm Samuel Thibault wrote: > Jeff Squyres, le Mon 21 Jun 2010 10:48:13 -0400, a écrit : > > I still see -rpath being inserted in the final link step for libhwloc.so > > (SVN build using AC 2.65, AM 1.11.1, LT 2.2.6b): > > > > /bin/sh ../libtool --tag=CC

[hwloc-devel] hwloc and rpath

me} %{_includedir}/%{name}/* %{_includedir}/%{name}.h %dir %{_defaultdocdir}/%{name}-%{version} %{_defaultdocdir}/%{name}-%{version}/*c %changelog * Fri Jun 18 2010 Jirka Hladky <jhla...@redhat.com> - 1.0.1-1 - Initial build Summary: Portable Hardware Locality - portable abstraction of hierarchi