Re: [hwloc-users] question about hwloc_set_area_membind_nodeset

2017-11-12 Thread Samuel Thibault
Brice Goglin, on dim. 12 nov. 2017 05:19:37 +0100, wrote: > That's likely what's happening. Each set_area() may be creating a new "virtual > memory area". The kernel tries to merge them with neighbors if they go to the > same NUMA node. Otherwise it creates a new VMA. Mmmm, that sucks. Ideally

Re: [hwloc-users] linkspeed in hwloc_obj_attr_u::hwloc_pcidev_attr_s struct while traversing topology

2017-10-13 Thread Samuel Thibault
Hello, TEJASWI k, on ven. 13 oct. 2017 14:44:53 +0530, wrote: > Thanks I could get the linkspeed when i tried with root user. > But is there no other way? See Brice's answer :) > And what is the reason behind this limitation? Ask Linux people, not us :) I can only guess that they are afraid

Re: [hwloc-users] linkspeed in hwloc_obj_attr_u::hwloc_pcidev_attr_s struct while traversing topology

2017-10-13 Thread Samuel Thibault
Hello, TEJASWI k, on ven. 13 oct. 2017 14:23:00 +0530, wrote: > All the other details I am able to query but linkspeed (pciObj->attr-> > bridge.upstream.pci.linkspeed) is always 0. > Do I need to enable any other flag to get linkspeed or am I going wrong > somewhere? You need to run as root for

[hwloc-users] process names in lstopo --ps

2017-08-23 Thread Samuel Thibault
Hello, The other day I modified the output of lstopo --ps to contain the end of the cmdline instead of the beginning, because with module systems, spack, etc. the path to application binaries get longer and longer, and eventually the actual name of the binary goes away on the right. But

Re: [hwloc-users] ? Finding cache & pci info on SPARC/Solaris 11.3

2017-06-08 Thread Samuel Thibault
Hello, Maureen Chew, on jeu. 08 juin 2017 10:51:56 -0400, wrote: > Should finding cache & pci info work? AFAWK, there is no user-available way to get cache information on Solaris, so it's not implemented in hwloc. Concerning pci, you need libpciaccess to get PCI information. Samuel

Re: [hwloc-users] Building hwloc for X11 on Mac OS X

2017-05-08 Thread Samuel Thibault
Hello, Gunter, David O, on jeu. 04 mai 2017 20:44:16 +, wrote: > launching lstopo always produces the text-based output. I cannot seem > to get the X-display features to work. And yes, I am able to launch > xterms and other X11-based apps correctly. Do you have the DISPLAY environment

Re: [hwloc-users] Building hwloc for a Cray/KNL system

2017-01-27 Thread Samuel Thibault
Hello, Gunter, David O, on Fri 27 Jan 2017 18:05:44 +, wrote: > $ aprun -n 1 -L 193 ~hwloc-tt/bin/lstopo-no-graphics Does aprun give you allocation of all cores? By default lstopo only shows the allocated cores. To see all of them, use the --whole-system option. Samuel

Re: [hwloc-users] Issue running hwloc on Xeon-Phi Coprocessor uOS

2017-01-17 Thread Samuel Thibault
Hello, Jacob Peter Caswell, on Tue 17 Jan 2017 11:43:07 -0600, wrote: > However, I'm still getting some make issues. After running make, I'm getting > the following output: > > x86_64-k1om-linux-ld: warning: libimf.so, needed by /home/caswell/hwloc/hwloc > /.libs/libhwloc.so, not found (try

Re: [hwloc-users] Issue running hwloc on Xeon-Phi Coprocessor uOS

2017-01-16 Thread Samuel Thibault
Hello, Jacob Peter Caswell, on Mon 16 Jan 2017 11:53:56 -0600, wrote: > x86_64-k1om-linux-ld: i386:x86-64 architecture of input file `.libs/support.o' > is incompatible with k1om output Did you make clean before reconfiguring+making? Samuel ___

Re: [hwloc-users] hwloc on Zynq

2016-12-12 Thread Samuel Thibault
Hello, Alberto Ortiz, on Mon 12 Dec 2016 18:03:23 +0100, wrote: > These gpios are included to the PS by looking into the device tree, and > located > in /sys/class. > I know hwloc is able to find PCI devices, but i would like to know if hwloc is > able to detect other type of I/O like the ones

Re: [hwloc-users] hwloc 1.11 in Android

2016-10-25 Thread Samuel Thibault
Hello, Brice Goglin, on Tue 25 Oct 2016 10:56:30 +0200, wrote: > It's not running as an > APK, but it's running inside a shell that was launched by an APK > (sshdroid, a ssh server shell). Not sure why this would be different? IIRC such shells have to circumvent some OS protections to run. So

Re: [hwloc-users] [hwloc-announce] Hardware Locality (hwloc) v1.11.3 released

2016-04-27 Thread Samuel Thibault
Brice Goglin, on Tue 26 Apr 2016 15:45:49 +0200, wrote: > The Hardware Locality (hwloc) team is pleased to announce the release > of v1.11.3: I'm getting one testsuite issue: FAIL: 16-2gr2gr2n2c+misc.xml (gdb) bt #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x77346d8e in

Re: [hwloc-users] Assembling multiple node XMLs

2015-10-30 Thread Samuel Thibault
Andrej Prsa, on Fri 30 Oct 2015 09:17:32 -0400, wrote: > > Can you have a startup script set > > HWLOC_XMLFILE=/common/path/${hostname}.xml in the system-wide > > environment? > > That's precisely what I'd been trying, but it proved exceedingly > difficult to figure out what environment file is

Re: [hwloc-users] Preferred Windows build environment

2015-04-03 Thread Samuel Thibault
Peyton, Jonathan L, le Fri 03 Apr 2015 21:35:23 +, a écrit : > I was curious what the preferred environment for building hwloc on Microsoft > Windows was. I would like to build a version that does not rely on any > libraries except the Microsoft C library and Kernel.dll’s. mingw should be

Re: [hwloc-users] Selecting real cores vs HT cores

2014-12-11 Thread Samuel Thibault
Jeff Squyres (jsquyres), le Thu 11 Dec 2014 21:12:27 +, a écrit : > When the BIOS is set to enable hyper threading, then several resources on the > core are split when the machine is booted up (e.g., some of the queue depths > for various processing units in the core are half the length that

Re: [hwloc-users] Processor numbering in Ivy-bridge

2014-09-29 Thread Samuel Thibault
Vishwanath Venkatesan, le Mon 29 Sep 2014 13:38:35 -0700, a écrit : > I was trying to use HWLOC on Ivybridge. I found that there is some > inconsistency in the core numbering. > > In the attached image (generated from running lstopo (hwloc - 1.9.1), we can > see that cores 6,7 do not exist

Re: [hwloc-users] hwloc-ls graphical output

2014-09-24 Thread Samuel Thibault
Dennis Jacobfeuerborn, le Thu 25 Sep 2014 02:01:48 +0200, a écrit : > The question I guess is how does the command determine the availability > of png as an output? Both cairo and libpng are installed. It depends on the backends which were built into cairo. Samuel

Re: [hwloc-users] Using hwloc to detect Hard Disks

2014-08-28 Thread Samuel Thibault
Hello, Pedaballe, Vineet, le Thu 28 Aug 2014 23:22:32 +, a écrit : > I am not able to figure out how to read Hard drive details, for e.g., > the content provided by hdparm application. > > My first question is, is it possible to read this using hwloc? If yes, can > anyone direct me to the

Re: [hwloc-users] BGQ question.

2014-03-25 Thread Samuel Thibault
Biddiscombe, John A., le Tue 25 Mar 2014 08:56:02 +, a écrit : > Looking at /proc/cpuinfo on the io node itself, I see only 60 cores listed. I > wonder if they’ve reserved one socket of 4 cores for IO purposes That's possible, yes. > and in fact hwloc is seeing the correct information. At

Re: [hwloc-users] [hwloc-announce] Hardware Locality (hwloc) v1.8.1 released

2014-02-13 Thread Samuel Thibault
Brice Goglin, le Thu 13 Feb 2014 23:18:04 +0100, a écrit : > IIRC, Windows warnings are function pointer casts that should be OK. IIRC too. Samuel

Re: [hwloc-users] Using hwloc to map GPU layout on system

2014-02-06 Thread Samuel Thibault
Brock Palen, le Thu 06 Feb 2014 21:31:42 +0100, a écrit : > GPU L#3 "nvml2" > GPU L#5 "nvml3" > GPU L#7 "nvml0" > GPU L#9 "nvml1" > > Is the L# always going to be in the oder I would expect? Because then I > already have my map then. No,

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

2014-01-28 Thread Samuel Thibault
Brice Goglin, le Tue 28 Jan 2014 12:46:24 +0100, a écrit : > 42: xchg %ebx,%rbx > > I guess having both ebx and rbx on these lines isn't OK. On Linux, I get > rsi instead of ebx, no problem. > > Samuel, any idea? Mmm, IIRC, "unsigned long" on windows may not be 64bit but 32bit? Perhaps we

Re: [hwloc-users] How to build hwloc static to link into a shared lib on Linux

2014-01-18 Thread Samuel Thibault
Erik Schnetter, le Sat 18 Jan 2014 07:29:37 +0100, a écrit : > You probably need to set CFLAGS in addition to CXXFLAGS. Yes, CXXFLAGS is for C++ files. hwloc doesn't have any :) It's CFLAGS which is for C. That being said, I wonder the gain you will have: all the probing functions will still

Re: [hwloc-users] [windows] hwloc_get_proc_cpubind issue, even with current process handle as 2nd parameter

2014-01-06 Thread Samuel Thibault
Samuel Thibault, le Mon 06 Jan 2014 18:07:59 +0100, a écrit : > Eloi Gaudry, le Mon 06 Jan 2014 17:16:53 +0100, a écrit : > > the PID of the process. I was assuming that casting this member to a HANDLE > > object would allow me to use hwloc_get_proc_cpubind, Let me fix my t

Re: [hwloc-users] [windows] hwloc_get_proc_cpubind issue, even with current process handle as 2nd parameter

2014-01-06 Thread Samuel Thibault
Eloi Gaudry, le Mon 06 Jan 2014 17:16:53 +0100, a écrit : > the PID of the process. I was assuming that casting this member to a HANDLE > object would allow me to use hwloc_get_proc_cpubind, No, PIDs are mere numbers, they have nothing to do with HANDLES. More interestingly, PID values are valid

Re: [hwloc-users] [windows] hwloc_get_proc_cpubind issue, even with current process handle as 2nd parameter

2014-01-06 Thread Samuel Thibault
Eloi Gaudry, le Mon 06 Jan 2014 16:37:55 +0100, a écrit : > AFAIK, the issue seems related to the GetAffinityMask call inside > hwloc_win_get_proc_cpubind : it always returns 0. So it's really the win32 layer which does not like seeing GetAffinityMask called. Just to make sure: you are using at

Re: [hwloc-users] [windows] hwloc_get_proc_cpubind issue, even with current process handle as 2nd parameter

2014-01-06 Thread Samuel Thibault
Eloi Gaudry, le Mon 06 Jan 2014 16:04:27 +0100, a écrit : > On Windows, hwloc_get_cpubind and hwloc_set_cpubind works correctly but I > cannot use hwloc_get_proc_cpubind or hwloc_set_proc_cpubind using the current > process handle as 2^nd parameter (no matter what the last one is). > > Any clue

Re: [hwloc-users] hwloc-bind --get on Solaris for binding to a single core

2013-02-06 Thread Samuel Thibault
Eugene Loh, le Wed 06 Feb 2013 07:50:02 +0100, a écrit : > How about adding a check upon entry to hwloc_solaris_get_sth_cpubind(): if > processor_bind() shows binding, report this and be done. If not, then > continue on with the lgroup logic that's already in that function. Yes? If

Re: [hwloc-users] Hwloc and Electric Fence (libefence).

2013-01-29 Thread Samuel Thibault
cesse...@free.fr, le Tue 29 Jan 2013 19:12:32 +0100, a écrit : > It was a very stupid question indeed ! Well, no it's not stupid :) Zero-allocs can indeed be frowned upon. Some algorithms like doing it, but some others to actually bug out at the same time allocating 0 bytes. Samuel

Re: [hwloc-users] hwloc tutorial material

2013-01-22 Thread Samuel Thibault
Kenneth A. Lloyd, le Mon 21 Jan 2013 22:46:37 +0100, a écrit : > Thanks for making this tutorial available. Using hwloc 1.7, how far down > into, say, NVIDIA cards can the architecture be reflected? Global memory > size? SMX cores? None of the above? None of the above for now. Both are

[hwloc-users] AIX test? Re: Hardware locality (hwloc) v1.6rc2 released

2012-11-21 Thread Samuel Thibault
Hello, Brice Goglin, le Tue 20 Nov 2012 15:26:37 +0100, a écrit : > I just released 1.6rc2 (mirrors will update soon). It seems fine in my tests, can somebody test on AIX? Samuel

Re: [hwloc-users] Windows api threading functions equivalent to hwloc?

2012-11-20 Thread Samuel Thibault
Andrew Somorjai, le Tue 20 Nov 2012 09:45:12 +0100, a écrit : > I'm also confused about these two lines and whether its necessary for the > second one to exist? > > HANDLE thread[num_threads]; > HANDLE pthread_getw32threadhandle_np(thread); > > Does the second api call fill the thread array or

Re: [hwloc-users] Windows api threading functions equivalent to hwloc?

2012-11-19 Thread Samuel Thibault
Andrew Somorjai, le Tue 20 Nov 2012 01:39:47 +0100, a écrit : > "CreateThread() and WaitForMultipleObjects() are not in hwloc since they have > nothing to do with topologies." > > I thought hwloc was also for threading? It can bind your threads, yes, but the way to create the thread is yours,

Re: [hwloc-users] Windows api threading functions equivalent to hwloc?

2012-11-19 Thread Samuel Thibault
Brice Goglin, le Mon 19 Nov 2012 21:09:33 +0100, a écrit : > hwloc_bitmap_t bitmap = hwloc_bitmap_alloc(); > hwloc_bitmap_set_only(bitmap, i); > hwloc_set_thread_cpubind(topology, m_threads[i], bitmap, 0); > hwloc_bitmap_free(bitmap); Or perhaps hwloc_set_thread_cpubind(topology, m_threads[i],

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.6rc1 released

2012-11-15 Thread Samuel Thibault
Hello, Brice Goglin, le Tue 13 Nov 2012 13:45:28 +0100, a écrit : > The Hardware Locality (hwloc) team is pleased to announce the first > release candidate for v1.6: I'm getting an odd failure in hwloc_pci_backend: lt-hwloc_pci_backend: hwloc-1.6rc1/tests/hwloc_pci_backend.c:68: main:

Re: [hwloc-users] Strange binding issue on 40 core nodes and cgroups

2012-11-05 Thread Samuel Thibault
Brice Goglin, le Mon 05 Nov 2012 23:23:42 +0100, a écrit : > top can also sort by the last used CPU. Type f to enter the config menu, > hilight the "last cpu" line, and hit 's' to make it the sort column. With older versions of top, type F, then j, then space. Samuel

Re: [hwloc-users] How do I access CPUModel info string

2012-10-29 Thread Samuel Thibault
Olivier Cessenat, le Sat 27 Oct 2012 19:10:55 +0200, a écrit : > Just in case, I also provide the output of sysctl hw: Thanks. There is indeed no package information (hw.packages), that's why hwloc does not include any socket object. Brice wrote: > One way to solve this problem (which may also

Re: [hwloc-users] How do I access CPUModel info string

2012-10-25 Thread Samuel Thibault
Robin Scher, le Thu 25 Oct 2012 23:57:38 +0200, a écrit : > ; eax = 0x8002 --> eax, ebx, ecx, edx: get processor name string > (part 1) > mov eax,0x8002 > cpuid Oh, this is indeed *exactly* the model name string. I only knew about the vendor_id string. > I don't

Re: [hwloc-users] How do I access CPUModel info string

2012-10-25 Thread Samuel Thibault
Robin Scher, le Thu 25 Oct 2012 23:39:46 +0200, a écrit : > Is there a way to get this string (e.g. "Intel(R) Core(TM) i7 CPU M 620 @ > 2.67GHz") consistently on Windows, Linux, OS-X and Solaris? Currently, no. hwloc itself does not have a table of such strings, and each OS has its own table.

Re: [hwloc-users] hwloc 1.5, freebsd and linux output on the same hardware

2012-10-05 Thread Samuel Thibault
Sebastian Kuzminsky, le Sat 06 Oct 2012 00:55:57 +0200, a écrit : > binding to CPU0 > could not bind to CPU0: Resource deadlock avoided Mmm, from what I read in the freebsd kernel: /* * Create a set in the space provided in 'set' with the provided parameters. * The set is returned with a

Re: [hwloc-users] hwloc 1.5, freebsd and linux output on the same hardware

2012-10-04 Thread Samuel Thibault
Sebastian Kuzminsky, le Wed 03 Oct 2012 17:24:55 +0200, a écrit : > So that's an improvement over the svn trunk > yesterday, but it's not all the way fixed yet! Ok. Apparemently hwloc can't bind itself to procs 0-9 for some reason. I have added debug to the trunk, could you try it again (no need

Re: [hwloc-users] hwloc 1.5, freebsd and linux output on the same hardware

2012-10-02 Thread Samuel Thibault
Hello, Sebastian Kuzminsky, le Wed 03 Oct 2012 01:08:46 +0200, a écrit : > Here you go (the list server rejected it because it was too big, but this > compressed version should make it through). Thanks! There were two bugs which resulted into cpuid not being properly compiled. I have fixed them

Re: [hwloc-users] hwloc 1.5, freebsd and linux output on the same hardware

2012-10-02 Thread Samuel Thibault
Sebastian Kuzminsky, le Wed 03 Oct 2012 00:35:48 +0200, a écrit : > [root@host-183 /home/nfshome/seb/tmp/hwloc-svn]# ./bin/lstopo > > > * CPU cpusets * > > cpu 0 (os 0) has cpuset 0x0001 ... > cpu 31 (os 31) has cpuset 0x8000 > Machine#0(local=0KB total=33493800KB Backend=x86

Re: [hwloc-users] hwloc 1.5, freebsd and linux output on the same hardware

2012-10-02 Thread Samuel Thibault
Hello, Sebastian Kuzminsky, le Tue 02 Oct 2012 23:47:05 +0200, a écrit : > I've attached the output from both platforms. On freebsd, could you pass --enable-debug to ./configure and rerun lstopo, to get more debugging information? Samuel

Re: [hwloc-users] Thread binding problem

2012-09-19 Thread Samuel Thibault
Hello, 2012/9/6 Brice Goglin > > Anyway, having 65000 mempolicies in use is a lot. And that would somehow > correspond to the number of set_area_membind that succeeed before one > fails. So the kernel might indeed fail to merge those. > > That said, these

Re: [hwloc-users] Solaris and hwloc

2012-09-14 Thread Samuel Thibault
Jeff Squyres, le Thu 13 Sep 2012 17:10:00 +0200, a écrit : > After a little more thought, I'm also thinking that having a "it's ok if > binding fails" CLI flag is a bad idea. If the user really wants something to > run without binding, then you can just do that in the shell: > > - >

Re: [hwloc-users] Solaris and hwloc

2012-09-12 Thread Samuel Thibault
Jeff Squyres, le Thu 13 Sep 2012 00:46:33 +0200, a écrit : > On Sep 12, 2012, at 6:44 PM, Samuel Thibault wrote: > > >> Anyone have an opinion? I'm 60/40 in favor of not letting it run, under > >> the rationale that the user asked for something that we can't delive

Re: [hwloc-users] Solaris and hwloc

2012-09-12 Thread Samuel Thibault
Jeff Squyres, le Thu 13 Sep 2012 00:45:56 +0200, a écrit : > On Sep 12, 2012, at 6:42 PM, Samuel Thibault wrote: > > No, we have it, but not all solaris systems have it. > > > Ah, I see. So if Siegmar had done "hwloc-bind socket:0 ..." -- assuming his > system

Re: [hwloc-users] Solaris and hwloc

2012-09-12 Thread Samuel Thibault
Jeff Squyres, le Thu 13 Sep 2012 00:25:24 +0200, a écrit : > On Sep 12, 2012, at 10:28 AM, Samuel Thibault wrote: > > >> He seems to get an hwloc error any time he tries to bind to more than 1 > >> PU. Is that expected on Solaris? > > > > Wit

Re: [hwloc-users] Solaris and hwloc

2012-09-12 Thread Samuel Thibault
I forgot to answer this: Jeff Squyres, le Wed 12 Sep 2012 16:16:57 +0200, a écrit : > Sidenote: if hwloc-bind fails to bind, should we still launch the child > process? Well, it's up to you to decide :) Samuel

Re: [hwloc-users] Solaris and hwloc

2012-09-12 Thread Samuel Thibault
Jeff Squyres, le Wed 12 Sep 2012 16:16:57 +0200, a écrit : > He seems to get an hwloc error any time he tries to bind to more than 1 PU. > Is that expected on Solaris? Without lgrp support, unfortunately yes: the processor_bind solaris interface only permits to bind to one processor. With

Re: [hwloc-users] Thread binding problem

2012-09-06 Thread Samuel Thibault
Gabriele Fatigati, le Thu 06 Sep 2012 10:12:38 +0200, a écrit : > mbind hwloc_linux_set_area_membind()  fails: > > Error from HWLOC mbind: Cannot allocate memory  Ok. mbind is not really supposed to allocate much memory, but it still does allocate some, to record the policy > //

Re: [hwloc-users] lstopo and GPus

2012-08-29 Thread Samuel Thibault
Gabriele Fatigati, le Wed 29 Aug 2012 16:56:30 +0200, a écrit : > The id showed in the GPU box from lstopo, is the same device_id CUDA > numeration > used in some function like setDevice() for example? Exactly. Samuel

Re: [hwloc-users] lstopo and GPus

2012-08-28 Thread 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 the cuda runtime during ./configure. You will then get new "cuda" devices. > Another question: the GPU

Re: [hwloc-users] lstopo and GPus

2012-08-28 Thread Samuel Thibault
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

2012-08-28 Thread Samuel Thibault
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

Re: [hwloc-users] q about mem binding API usage

2012-05-31 Thread Samuel Thibault
Vlad, le Thu 31 May 2012 18:07:43 +0200, a écrit : > Thanks a lot ! This is exactly the kind of clarification I've been looking for > and it's great to know it's been added to the official docs. It's always better to answer a question by putting yet more doc :) Samuel

Re: [hwloc-users] q about mem binding API usage

2012-05-31 Thread Samuel Thibault
Hello, Vlad, le Thu 31 May 2012 16:49:00 +0200, a écrit : > This might be a naive question, but I'd like to clarify nonetheless: to > provide > any sort of affinity guarantees, hwloc mem binding APIs assume that any memory > allocation is done exclusively via hwloc_alloc_membind() and friends? 

Re: [hwloc-users] Hwloc error.

2012-05-30 Thread Samuel Thibault
Hello, John Hanks, le Wed 30 May 2012 17:03:47 +0200, a écrit : > * Hwloc has encountered what looks like an error from the operating system. > * > * object intersection without inclusion! > * Error occurred in topology.c line 594 There is indeed something odd with what the Linux kernel reports:

Re: [hwloc-users] possible concurrency issue with reading /proc data on Linux

2012-04-21 Thread Samuel Thibault
Vlad, le Sat 21 Apr 2012 23:37:11 +0200, a écrit : > 433 /* take the number of links as a good estimate for the number of tids */ > 434 if (fstat(dirfd(taskdir), ) == 0) > 435max_tids = sb.st_nlink; > > "taskdir" here is /proc//task, correct? In which case the threads will be > doing

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-15 Thread Samuel Thibault
Samuel Thibault, le Thu 15 Mar 2012 07:42:40 +0100, a écrit : > Brice Goglin, le Wed 14 Mar 2012 22:32:07 +0100, a écrit : > > We debugged this in private emails with Hartmut. His 48-core platform is > > now detected properly. Everything got fixed with a patch > > functionna

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-14 Thread Samuel Thibault
Samuel Thibault, le Wed 14 Mar 2012 18:16:37 +0100, a écrit : > Hartmut Kaiser, le Wed 14 Mar 2012 08:52:59 -0500, a écrit : > > > > > Le 14/03/2012 09:39, Brice Goglin a écrit : > > > > Le 13/03/2012 19:08, Hartmut Kaiser a écrit : > > > >>> -

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-14 Thread Samuel Thibault
Hartmut Kaiser, le Wed 14 Mar 2012 08:52:59 -0500, a écrit : > > > Le 14/03/2012 09:39, Brice Goglin a écrit : > > > Le 13/03/2012 19:08, Hartmut Kaiser a écrit : > > >>> - hwloc_bitmap_from_ith_ulong(obj->cpuset, > > GroupMask[i].Group, > > >>> GroupMask[i].Mask); > > >>> +

Re: [hwloc-users] V1.4.1: Windows x64 import library broken

2012-03-14 Thread Samuel Thibault
Hartmut Kaiser, le Mon 12 Mar 2012 23:05:44 +0100, a écrit : > The import library libhwloc.lib distributed with the Windows x64 binaries is > broken in V1.4.1 (even if it was ok in V1.4). The library internally refers > to libhwloc-4.dll (instead of libhwloc-5.dll). While it is not a problem to >

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-13 Thread Samuel Thibault
Brice Goglin, le Tue 13 Mar 2012 20:09:57 +0100, a écrit : > Thanks. The remaining problems don't look obvious. Something strange > seems to happen right after the windows backend added all objects. I > wonder if we have some problems in the bitmap management code. Can you > try to run some tests

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-13 Thread Samuel Thibault
Brice Goglin, le Tue 13 Mar 2012 18:55:29 +0100, a écrit : > Le 13/03/2012 17:04, Hartmut Kaiser a écrit : > >>> But the problems I was seeing were not MSVC specific. It's a > >>> proliferation of arcane (non-POSIX) function use (like strcasecmp, > >>> etc.) missing use of HAVE_UNISTD_H,

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-13 Thread Samuel Thibault
Jeffrey Squyres, le Tue 13 Mar 2012 17:23:02 +0100, a écrit : > Is the implication here that some flavors of windows have 32 bit ulongs? win32/64 is a platform where ulong is always 32bit. > And we need to deal with that? Or is this a compiler-specific issue? (i.e., > mingw doesn't have these

Re: [hwloc-users] Problems on SMP with 48 cores

2012-03-13 Thread Samuel Thibault
Samuel Thibault, le Tue 13 Mar 2012 13:33:05 +0100, a écrit : > > I tried to recompile the library using MSVC which would allow me to debug > > the issue, but after several hours of tweaking I gave up. As it turns out > > the code base is everything but portable, which is

Re: [hwloc-users] Object Depth

2012-03-13 Thread Samuel Thibault
Marwan Abd Ellah, le Tue 13 Mar 2012 11:33:18 +0100, a écrit : > I was using the HWLoc library v 1.4.1 for getting a cpuset of the socket > connected to a certain PCI device (mainly GPU). When I was trying to print the > topology tree I got the following  > Machine#0(12GB) >   Socket#0 >    

Re: [hwloc-users] Hardware Topology

2012-02-28 Thread Samuel Thibault
vaibhav dutt, le Tue 28 Feb 2012 23:42:58 +0100, a écrit : > I got the details from hwloc. > I just wanted to know whether cores 0,4 and 2,6 are on  separate dies or the > same die? It's the same die, die #0: Socket L#1 starts only after that. Again, use lstopo -.txt as it's more intuitive.

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.4 released

2012-02-14 Thread Samuel Thibault
Hello, Jiri Hladky, le Wed 15 Feb 2012 01:38:44 +0100, a écrit : > I have found one minor issue - file hwloc-assembler-remote does not have > executable bit set. I had to add following to the RPM SPEC file to fix it: > > %{__chmod} 0755 %{buildroot}%{_bindir}/hwloc-assembler-remote That's odd:

Re: [hwloc-users] build issue with CFLAGS='-mcmodel=medium'

2012-01-31 Thread Samuel Thibault
Could you try the attached patch? Samuel Index: include/private/cpuid.h === --- include/private/cpuid.h (révision 4210) +++ include/private/cpuid.h (copie de travail) @@ -1,5 +1,5 @@ /* - * Copyright © 2010-2011 Université

Re: [hwloc-users] creation and destruction of bound threads

2012-01-30 Thread Samuel Thibault
Albert Solernou, le Mon 30 Jan 2012 12:37:31 +0100, a écrit : > I am working on a threaded code, and want to bind threads to cores. However, > the process creates and destroys the threads, so here is the question: > What happens if I enter on a threaded part of the code, bind "thread X" to > a

Re: [hwloc-users] Bogus files in 64bit Windows binary distribution (1.4rc1)

2012-01-19 Thread Samuel Thibault
Hartmut Kaiser, le Fri 20 Jan 2012 00:43:32 +0100, a écrit : > > Hartmut Kaiser, le Thu 19 Jan 2012 22:48:50 +0100, a écrit : > > > We are using hwloc with VS2010 and were happy to realize that after > > > the (for > > > us) totally broken Windows binary distribution in V1.3 > > > > Broken? How

Re: [hwloc-users] hwloc_get_last_cpu_location and hwloc_get_cpubind

2012-01-17 Thread Samuel Thibault
Marc-André Hermanns, le Tue 17 Jan 2012 15:15:12 +0100, a écrit : > write(1, "This system has 4 levels\n", 25) = 25 > open("/proc/self/task", > O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 4 > fcntl64(4, F_GETFD) = 0x1 (flags FD_CLOEXEC) > fstat64(4,

Re: [hwloc-users] hwloc_get_last_cpu_location and hwloc_get_cpubind

2012-01-17 Thread Samuel Thibault
Marc-André Hermanns, le Tue 17 Jan 2012 11:47:43 +0100, a écrit : > It seems now that it has the whole system in the cpuset. How can I > really infer the PU this process was run on? I would have expected the > cpuset to have only 1 element per level to indicate the path from > machine to PU.

Re: [hwloc-users] hwloc_get_last_cpu_location and hwloc_get_cpubind

2012-01-16 Thread Samuel Thibault
Hello, Marc-André Hermanns, le Mon 16 Jan 2012 14:01:23 +0100, a écrit : > hwloc_get_last_cpu_location(topology, cpuset, 0); > > and I am at a total loss on what I should make of this. It seems I am > doing something fundamentally wrong, You need to check the value returned by the

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-13 Thread Samuel Thibault
Andrew Helwer, le Fri 13 Jan 2012 18:16:16 +0100, a écrit : > libhwloc.lib(traversal.o) : error LNK2019: unresolved external symbol > __ms_vsnpr > intf referenced in function snprintf Do you also link msvcrt in? mingw needs it for almost everything. Samuel

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-13 Thread Samuel Thibault
Andrew Helwer, le Fri 13 Jan 2012 18:09:11 +0100, a écrit : > > You can perhaps try to rename it into a .lib file and give that to VS. > > Didn't work. What errors do you get? Samuel

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Samuel Thibault, le Fri 13 Jan 2012 02:01:12 +0100, a écrit : > Andrew Helwer, le Fri 13 Jan 2012 01:51:15 +0100, a écrit : > > I'm not sure I understand. Can you link to .a files with VS? > > I don't know, but what's sure is that .a files are static libraries in > mingw. Y

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Andrew Helwer, le Fri 13 Jan 2012 01:51:15 +0100, a écrit : > I'm not sure I understand. Can you link to .a files with VS? I don't know, but what's sure is that .a files are static libraries in mingw. > I tried linking to the .lib file in the 64-bit release. I get only unresolved > external

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Andrew Helwer, le Fri 13 Jan 2012 01:35:27 +0100, a écrit : > It fails with the following: > > *** Warning: linker path does not have real file for library -lgdi32. Ah, that's a dark bug in libtool. > gcc -I/cygdrive/c/hwloc-asdf/include -I/cygdrive/c/hwloc-asdf/include > -I/cygdriv >

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Andrew Helwer, le Tue 10 Jan 2012 02:08:46 +0100, a écrit : > the Visual Studio compiler runs into a lot of issues. What kind of issues for instance? Samuel

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Hello, Andrew Helwer, le Tue 10 Jan 2012 02:08:46 +0100, a écrit : > First of all, is Windows 64-bit supported? There is only a 32-bit release on > the downloads page. I have tried mingw-w64, and it does seem to work, I have added a 64-bit release on the download page (pending mirror push).

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-12 Thread Samuel Thibault
Hello, Andrew Helwer, le Thu 12 Jan 2012 02:11:58 +0100, a écrit : > If I run the command manually, it can't find the libhwloc.def file. Which is > reasonable, as it does not appear to exist in the .lib directory. Am I > missing something? In principle the .def file is generated by the linker.

Re: [hwloc-users] Compiling hwloc into a static library on Windows and Linux

2012-01-09 Thread Samuel Thibault
Andrew Helwer, le Tue 10 Jan 2012 02:08:46 +0100, a écrit : > First of all, is Windows 64-bit supported? There is only a 32-bit release on > the downloads page. I have never tried to build a 64bit binary, but there is little reason it should fail. > However, when I specify the

Re: [hwloc-users] GPU/NIC/CPU locality

2011-11-29 Thread Samuel Thibault
Stefan Eilemann, le Tue 29 Nov 2011 11:40:18 +0100, a écrit : > Maybe I'm missing something, but I don't see any PCI-related output with > lstopo. You are probably missing the libpci-devel package. Samuel

Re: [hwloc-users] Process and thread binding

2011-09-12 Thread Samuel Thibault
Gabriele Fatigati, le Mon 12 Sep 2011 15:50:45 +0200, a écrit : > thanks very much for your explanations. But I don't understand why a process > inherits core bound of his threads On Linux, there is no such thing as "process binding", only "thread binding". hwloc emulates the former by using the

Re: [hwloc-users] Re : Re : hwloc topology check initializing

2011-09-03 Thread Samuel Thibault
Gabriele Fatigati, le Sat 03 Sep 2011 16:09:11 +0200, a écrit : > What about hwloc_topology check()? > > What types of check does? Mostly that the hwloc library itself didn't do anything wrong. Samuel

Re: [hwloc-users] hwloc_get_last_cpu_location and PU

2011-08-29 Thread Samuel Thibault
Gabriele Fatigati, le Mon 29 Aug 2011 16:16:25 +0200, a écrit : > hwloc_get_last_cpu_location() return last CPU where process/thread ran.On  SMT > machine, it return the PU where   process/thread ran ? Yes, sure, since what it returns is an OS CPU bitmask. Samuel

Re: [hwloc-users] Numa availability

2011-08-28 Thread Samuel Thibault
Gabriele Fatigati, le Sun 28 Aug 2011 14:47:33 +0200, a écrit : > in each case, if get_nbobjs_by_type return 0, also if the machine is NUMA, > hwloc can't build the NUMA-aware topolog, so the NUMA capability is not > usable. > Is it right? I'm not sure to understand how you relate these

Re: [hwloc-users] Numa availability

2011-08-28 Thread Samuel Thibault
Brice Goglin, le Sun 28 Aug 2011 12:36:31 +0200, a écrit : > > Is there a hwloc routine to check this? > > get_nbobjs_by_type(topology, HWLOC_OBJ_NODE) tells how many NUMA node > objects exist. > If you get >1, the machine is NUMA. > If the non-NUMA case, I think you can get 0 or 1 depending on

Re: [hwloc-users] [hwloc-announce] Hardware Locality (hwloc) v1.2.1rc3 released

2011-08-16 Thread Samuel Thibault
Brice Goglin, le Tue 16 Aug 2011 19:49:10 +0200, a écrit : > hwloc 1.2.1 *rc3* is out (web mirrors will update shortly). It fixes > hwloc_get_last_cpu_location() for Linux threads. Apart from that, > nothing important. Let's hope this one will become the final 1.2.1 > within a couple days. Since

Re: [hwloc-users] Magny Cours L3 cache issue

2011-08-16 Thread Samuel Thibault
Wheeler, Kyle Bruce, le Tue 16 Aug 2011 16:52:54 +0200, a écrit : > hwloc-gather-topology doesn't seem to work on my compute nodes... not sure > why. It doesn't report any failures, but it doesn't create the tarball either > (just spits out more lstopo output). Maybe try to replace /bin/sh with

Re: [hwloc-users] Re : lstopo on multiple machines

2011-08-16 Thread Samuel Thibault
Jeff Squyres, le Tue 16 Aug 2011 16:09:24 +0200, a écrit : > I'd be against hwloc automatically spreading across multiple machines. I > think there are plenty of tools to do that already. I fully agree. There is no way to be able to interact with each and every job scheduler anyway. > That

Re: [hwloc-users] Get CPU associated to a thread

2011-08-12 Thread Samuel Thibault
Hello, PULVERAIL Sébastien, le Fri 12 Aug 2011 13:59:46 +0200, a écrit : > Does a such function exist ? See hwloc_get_last_cpu_location() Samuel

Re: [hwloc-users] hwloc get cpubind function

2011-08-11 Thread Samuel Thibault
Gabriele Fatigati, le Thu 11 Aug 2011 18:26:28 +0200, a écrit : > Gabriele Fatigati, le Thu 11 Aug 2011 18:05:25 +0200, a écrit : > > char* bitmap_string=(char*)malloc(256); > > > > hwloc_bitmap_t set = hwloc_bitmap_alloc(); > > > > hwloc_linux_get_tid_cpubind(, tid, set);

Re: [hwloc-users] hwloc get cpubind function

2011-08-11 Thread Samuel Thibault
Gabriele Fatigati, le Thu 11 Aug 2011 18:05:25 +0200, a écrit : > char* bitmap_string=(char*)malloc(256); > > hwloc_bitmap_t set = hwloc_bitmap_alloc(); > > hwloc_linux_get_tid_cpubind(, tid, set); Where does "tid" come from? hwloc_linux_get_tid_cpubind() only takes Linux tids (as in gettid()),

Re: [hwloc-users] hwloc get cpubind function

2011-08-11 Thread Samuel Thibault
Gabriele Fatigati, le Thu 11 Aug 2011 10:32:23 +0200, a écrit : > I'm using hwloc-1.3a1r3606.  Now hwloc_get_last_cpu_location() works well: > > thread 0  bind:  0x0008   as core number 3 > thread 1 bind: 0x0800 as core number 11 Good. > but hwloc_linux_get_tid_cpubind() has still some

Re: [hwloc-users] hwloc get cpubind function

2011-08-10 Thread Samuel Thibault
Samuel Thibault, le Wed 10 Aug 2011 16:24:39 +0200, a écrit : > Gabriele Fatigati, le Wed 10 Aug 2011 16:13:27 +0200, a écrit : > > there is something wrong. I'm using two thread, the first one is bound on > > HWLOC_OBJ_PU number 2, the second one on  HWLOC_OBJ_PU number 10

  1   2   >