Re: [hwloc-users] howloc with scalemp

Brock Palen wrote: > [brockp@nyx0809 INTEL]$ lstopo - > System(79GB) > Misc0 > Node#0(10GB) + Socket#1 + L3(8192KB) > L2(256KB) + L1(32KB) + Core#0 + P#0 > L2(256KB) + L1(32KB) + Core#1 + P#1 > L2(256KB) + L1(32KB) + Core#2 + P#2 > L2(256KB) + L1(32KB) + Core#3 + P#3

Re: [hwloc-users] Creating a D wrapper around hwloc

Jim Burnes wrote: > I can make these available to D in several different ways, but I need > to know the true intent of marking them as "static __inline". > > 1. Are they marked that way simply to increase performance? > No. > 2. Are they marked that way to avoid some sort of thread safety

Re: [hwloc-users] hwloc RPM spec file

On 23/04/2010 18:09, Jirka Hladky wrote: > Hello, > > I have written hwloc RPM spec file. It's attached. > > Thanks > Jirka > > Thanks Jirka, but don't you need some BuildRequires such as the following? libX11-devel libxml2-devel cairo-devel ncurses-devel Tony (CCed) also worked on RPMs for

Re: [hwloc-users] hwloc on systems with more than 64 cpus?

No, there is no such limit. If you have 128cores, the cpuset string will be 0x,0x,0x,0x As long as you have less than 1024 cores, everything should work fine. For more than 1024, you'll need to rebuild with a manual change in the source code, or wait for hwloc 1.1.

Re: [hwloc-users] hwloc on cray

Hello Norman, I don't think anybody ever tried. But we have an entry in the TODO list saying "port to cray catamount" :) If anybody wants to port hwloc on cray, we'd be happy to help. Getting us an access on a Cray machine might also help :) Brice Le 23/06/2010 04:05, Norman Lo a écrit : >

Re: [hwloc-users] hwloc sockets support on solaris

I see this in the solaris binding core: if (hwloc_cpuset_weight(hwloc_set) != 1) { errno = EXDEV; return -1; } OMPI doesn't get this error ? Brice Le 23/06/2010 21:56, Terry Dontje a écrit : > Does hwloc think it supports binding processes to sockets or multiple > cpus? I am

Re: [hwloc-users] hwloc sockets support on solaris

Le 23/06/2010 22:27, Jeff Squyres a écrit : > Hm. We should be. Here's the hwloc plugin code for setting CPU affinity > (it's static because it's invoked by function pointer): > > static int module_set(opal_paffinity_base_cpu_set_t mask) > { > int i, ret = OPAL_SUCCESS; > hwloc_cpuset_t

Re: [hwloc-users] Getting a graphics view for anon graphic system...

Le 09/06/2010 21:52, Brice Goglin a écrit : > Le 09/06/2010 21:41, Jeff Squyres a écrit : > >> On Jun 6, 2010, at 4:03 PM, Olivier Cessenat wrote: >> >> >> >>> What you write is clear to computer scientists, but I failed to figure >&g

Re: [hwloc-users] hwloc_set/get_thread_cpubind

Le 14/07/2010 20:28, Αλέξανδρος Παπαδογιαννάκης a écrit : > hwloc_set_thread_cpubind and hwloc_get_thread_cpubind are missing from the > html documentation > http://www.open-mpi.org/projects/hwloc/doc/v1.0.1/group__hwlocality__binding.php > > It may be

Re: [hwloc-users] xmlbuffer test failure

Looks like there's something specific to your machine. Can you send the XML output of lstopo ? thanks Brice Le 05/11/2010 05:41, ryuuta a écrit : > Hi, > > I'd like to report the failure of the one of the tests run by 'make > check': > > exported to buffer 0x8546408 length 3070 > re-exported

Re: [hwloc-users] xmlbuffer test failure

Here's the patch :) Le 05/11/2010 08:10, Brice Goglin a écrit : > Interesting, you don't have any hugepage information, it's probably > disabled in the kernel. Can you apply th attached patch and check that > the XML output only contains a single "page_type" line and th

Re: [hwloc-users] hwloc@SC10

; > Drop by the Cisco booth for the exact schedule; we're right next to the main > SciNet NOC. > > See you there! > > > > On Nov 8, 2010, at 11:22 AM, Brice Goglin wrote: > > >> Hello, >> For those of you going to SC10 @ New Orleans next week, you should kno

Re: [hwloc-users] Identifying NIC in a topology using HWLOC

Hello Saktheesh, NICs do not appear in the topology yet. This is under development in the libpci branch. You can take a look at https://svn.open-mpi.org/svn/hwloc/branches/libpci and tell us what you think of the interface. If you're talking about infiniband NICs, hwloc/openfabrics-verbs.h

Re: [hwloc-users] Problem getting cpuset of MPI task

Le 09/02/2011 16:53, Hendryk Bockelmann a écrit : > Since I am new to hwloc there might be a misunderstanding from my > side, but I have a problem getting the cpuset of MPI tasks. I just > want to run a simple MPI program to see on which cores (or CPUs in > case of hyperthreading or SMT) the tasks

Re: [hwloc-users] hwloc-ps output - how to verify process binding on the core level?

Le 14/02/2011 07:43, Siew Yin Chan a écrit : > >> >> > > No. Each hwloc-bind command in the mpirun above doesn't know that > there are other hwloc-bind instances on the same machine. All of > them bind their process to all cores in the first socket. > > => Agree. For socket:0.core:0-3

Re: [hwloc-users] on using hwloc_get_area_membind_nodeset

Le 05/07/2011 20:13, Alfredo Buttari a écrit : > Hi all, > if I understand correctly this routine can tell on which NUMA node(s) > a specific memory area resides, is this correct? > Will this routine work on any memory area allocated with any > allocation routine other than those provided by

Re: [hwloc-users] on using hwloc_get_area_membind_nodeset

be I can get away with a single call to get_mempolicy (no need to > check for all the pages in the memory area). > Thanks again > > best regards > alfredo > > > On Tue, Jul 5, 2011 at 8:34 PM, Brice Goglin <brice.gog...@inria.fr> wrote: >> Hello, >> >>

Re: [hwloc-users] Thread core affinity

Le 01/08/2011 12:16, Gabriele Fatigati a écrit : > Hi, > > reading a hwloc-v1.2-a4 manual, on page 15, i look an example > with 4-socket 2-core machine with hyperthreading. > > Core id's are not exclusive as said before. PU's id are exclusive but > not physically sequential (I suppose) > > PU P#0

Re: [hwloc-users] Thread core affinity

Le 01/08/2011 14:47, Gabriele Fatigati a écrit : > Hi Brice, > > so, if I inderstand well, PU P# numbers are not the same specified > as HWLOC_OBJ_PU flag? > > 2011/8/1 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > Le 01/08/2011 12:

Re: [hwloc-users] Thread core affinity

gt; "P#" prefix means "physical index". > > But from the hwloc manual, page 58: > > > HWLOC_OBJ_PU: Processing Unit, or (Logical) Processor.. > > > but it is in conflict with what you said :( > > > 2011/8/1 Brice Goglin <brice.gog...@inria.

Re: [hwloc-users] Thread core affinity

ine, > PU# are sequential (page 17), and in a non NUMA machine are not > sequential? ( page 16) > > 2011/8/1 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > You're confusing object types with index types. > > PU is an object

Re: [hwloc-users] hwloc varning flag

I think I am seeing this too on a custom program, so probably not your application's fault. Brice Le 13/08/2011 10:37, Gabriele Fatigati a écrit : > > > Dearhwloc users and developers, > > I'm using hwloc 1.2 stable version Intel 11 compiled and checking my > little application with valgrind

Re: [hwloc-users] hwloc varning flag

FWIW it's worth, it's a "bug" in valgrind. The manpage of mbind does not exactly match the kernel requirements on mbind parameters. And valgrind fails at respecting the manpage anyway. See https://bugs.kde.org/show_bug.cgi?id=280083 for the mess... Brice Le 13/08/2011 15:07, Br

[hwloc-users] Re : hwloc varning flag

No it just means that valgrind could properly check how hwloc uses mbind. But I checked the hwloc code again, things look ok, and the kernel is happy with our mbind parameters. Brice - Reply message - De : "Gabriele Fatigati" <g.fatig...@cineca.it> Pour?: "Bri

[hwloc-users] Re : lstopo on multiple machines

Hello Seb, Hwloc only looks at the local machine, there's no support for multinode topology detection so far. We are considering adding it but we don't know yet what users want to do with it, if it should be in the core or not, automatic or nor. Your feedback is welcome. Brice - Reply

Re: [hwloc-users] Bind current thread to a specific cpu

Are you talking about logical ids (the one given by hwloc) or physical/OS ids (the one given by the OS and possibly in strange order) ? You should avoid using physical ids, but... If logical, you can hwloc_get_obj_by_type() to get the corresponding object, then use its ->cpuset. If physical, you

Re: [hwloc-users] Numa availability

Le 28/08/2011 12:14, Gabriele Fatigati a écrit : > Dear hwloc users, > > what happens if I use hwloc on a non-NUMA machine? I suppose memory > binding has no sense because there is not a memory locality concept. > And regards execution binding? are there some difference on a non-NUMA > machine?

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

nitializing Date : sam., sept. 3, 2011 15:26 Hi Brice, but it works only if the user assing NULL to topology. hwloc_topology_init() does not check the argument passed ? There are no ways to check if topology is initialized or not? Thanks. 2011/9/3 Brice Goglin <brice.gog...@inria.fr>

Re: [hwloc-users] Process and thread binding

Le 12/09/2011 13:29, Gabriele Fatigati a écrit : > Hi Birce, > > I'm so confused.. > > I'm binding MPI processes with set_cpu_bind and it works well. The > problem is when I try to bind process and threads. > > It seem that thread process influence bind of main thread. > > And from hwloc manual:

Re: [hwloc-users] Process and thread binding

Le 12/09/2011 14:17, Gabriele Fatigati a écrit : > Mm, and why? In a hybrid code ( MPI + OpenMP), my idea is to bind a > single MPI process in one core, and his threads in other cores. > Otherwise I have all threads that runs on a single core. > The usual way to do that is to first bind the

Re: [hwloc-users] hwloc set membind function

Le 22/09/2011 12:20, Gabriele Fatigati a écrit : > NUMA node(s) near the specified cpuset. > > What does "nodes near the specified cpuset" means? The node wherethe > specified cpuset lives? > Set the default memory binding policy of the current process or thread > to prefer the The node near

Re: [hwloc-users] hwloc set membind function

Le 25/09/2011 11:14, Gabriele Fatigati a écrit : > > I report my questions in a different way (in the first question i did > a mistake): > > > 1) I don't understand the means of set_membind() function. Why I > should to allocate in a node "near" my cpuset and not in my local node > (where thread

Re: [hwloc-users] hwloc set membind function

Le 25/09/2011 12:19, Gabriele Fatigati a écrit : > Hi Brice, > > >The flag says "when the first touch occurs and the physical memory is > allocated for real, don't allocate on the local node (default), but > >rather allocate where specified by set_membind". > > If is it already allocated for real,

Re: [hwloc-users] hwloc set membind function

Le 25/09/2011 20:27, Gabriele Fatigati a écrit : > if(tid==0){ > > set_membind(HWLOCMEMBIND_BIND, node 0) > malloc(array)... > > } > > if (tid==1){ > set_membind(HWLOCMEMBIND_BIND, node 1) > > for(i...) > array(i) > } > > end parallel region > > > array is allocated on node 1, not node 0 as I

Re: [hwloc-users] hwloc set membind function

ble? I just said "you have to touch right after malloc." Brice > > 2011/9/25 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > Le 25/09/2011 20:57, Gabriele Fatigati a écrit : > > after done this, memory is allocated not

Re: [hwloc-users] How to combine hwloc-bind and mpirun

Le 10/11/2011 13:13, Rafael R. Pappalardo a écrit : > I am trying to send a MPI job to selected cores on a 64 cores machine. With > taskset I use: > > mpirun -np 8 taskset -c 1,3,5,7,9,11,13,15 program > > but if I substitute taskset by hwloc-bind doing > > mpirun -np 8 hwloc-bind core:1 core:3

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

Hello Stefan, hwloc 1.3 already has support for PCI device detection. These new objects contain a "class" field that can help you know if it's a NIC/GPU/... However it's hard to know which PCI device is eth0 or eth1, so we also try to add some OS device inside PCI device. If you're using Linux,

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

> Hwloc optional build support status (more details can be found above): > > Probe / display PCI devices: yes > Graphical output (Cairo):yes > XML output: full "XML output" should be "XML input/output" or "XML support". > Memory support: binding, set policy,

[hwloc-users] removing old cpuset API?

Dear hwloc users, The cpuset API (hwloc_cpuset_*) was replaced by the bitmap API (hwloc_bitmap_*) in v1.1.0, back in december 2010. We kept backward compatibility by #defin'ing the old API on top of the new one. So you may stil use the old API in your application (but you would get "deprecated"

[hwloc-users] hwloc and HTX device ?

Hello, I'd like to see what hwloc reports on AMD machines with a HTX card (hypertransport expansion card). The most widely known case would likely be a 3-5-years old AMD cluster with Pathscale Infinipath network cards. But I think there are also some accelerators such as clearspeed, and the

Re: [hwloc-users] receive 0x0 from hwloc_cuda_get_device_cpuset

Le 21/02/2012 15:42, Albert Solernou a écrit : > Hi, > I have several questions in order to fix this issue from the machine > side. > > 1) I realised that on this machine neither libcpuset nor cpuset-utils > are installed. Could this be related to the problem? No, Linux "cpuset" are very

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

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, HAVE_STRINGS_H to wrap >>> non-standard headers, unsafe mixing of >>>

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

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, HAVE_STRINGS_H to wrap >>> non-standard headers, unsafe mixing of >>>

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

We debugged this in private emails with Hartmut. His 48-core platform is now detected properly. Everything got fixed with a patch functionnally-identical to what Samuel sent earlier. There's a bit of work before we can commit the fix, but Windows support for more than 32 cores will be officially

Re: [hwloc-users] Using distances

On 21/04/2012 12:23, Jeffrey Squyres wrote: I'm trying to use hwloc distances in Open MPI (e.g., find the distance from each OpenFabrics device to the PU(s) where this process is bound), and I'm a bit confused by the distances documentation. If I have a WHOLE_SYSTEM topology, and I know that

Re: [hwloc-users] Using distances

On 21/04/2012 13:15, Jeffrey Squyres wrote: On Apr 21, 2012, at 7:09 AM, Brice Goglin wrote: I assume you have the entire distance (latency) matrix between all NUMA nodes as usually reported by the BIOS. const struct hwloc_distance_s *distances = hwloc_get_whole_distance_matrix_by_type

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

On 21/04/2012 23:08, Vlad wrote: Greetings, I use hwloc-1.4.1 stable on Red Hat 5 and am seeing a possible concurrency issue not covered by the "Thread Safety" guidelines: - I start a small number (4) of threads, each of which does some work and periodically executes

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

On 21/04/2012 23:36, Vlad wrote: Will try this within a day or two. At the moment I am simply using a retry loop on ENOSYS and usually no more than one retry is needed. Ok thanks. You are probably correct. I was thinking of this code from

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

run out of retries I default to hwloc_get_last_cpu_location(... HWLOC_CPUBIND_THREAD) -- since presumably that can't fail and the result is technically valid given hwloc_get_last_cpu_location() semantics (it reads state that's inherently transient). On Apr 23, 2012, at 7:53 AM, Brice Goglin

Re: [hwloc-users] hwloc_get_last_cpu_location on AIX

Le 08/05/2012 14:33, Hendryk Bockelmann a écrit : > Hello, > > I just ran into trouble using hwloc_get_last_cpu_location on our > POWER6 cluster with AIX6.1 > My plan is to find out if the binding of the job-scheduler was correct > for MPI-tasks and OpenMP-threads. This is what I want to use: > >

Re: [hwloc-users] hwloc - Build problem.

Hello Anatoly, You likely need to add libxml2.a to your link command-line. And some others may be missing later. Instead of linking with src/.libs/libhwloc.a, you should run "make install" and use libhwloc.a from there (use --prefix= to tell configure where to install). Once hwloc is installed,

Re: [hwloc-users] hwloc_get_last_cpu_location on AIX

ing at get_last_cpu_location() for entire processes instead of individual threads. Brice Le 08/05/2012 14:41, Brice Goglin a écrit : > Le 08/05/2012 14:33, Hendryk Bockelmann a écrit : >> Hello, >> >> I just ran into trouble using hwloc_get_last_cpu_location on our >> PO

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

Le 06/08/2012 23:47, Wheeler, Kyle Bruce a écrit : > Hello, > > I'm failing to understand what hwloc (v1.5) is doing. I'm trying to use > hwloc_get_latency() to determine the distance between two cores. > > The two cores are on different sockets. According to libnuma's numactl, the > latency

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 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

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] Thread binding problem

upported > -1 with errno set to EXDEV if the binding cannot be enforced > > > Any other binding failure reason? The memory available is enought. > > 2012/9/5 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > Hello Gabriele, > > The on

Re: [hwloc-users] Thread binding problem

osed that these two case > was the two unique possibly. > > From the hwloc documentation: > > -1 with errno set to ENOSYS if the action is not supported > -1 with errno set to EXDEV if the binding cannot be enforced > > > Any other binding failure reason?

Re: [hwloc-users] Thread binding problem

Le 06/09/2012 09:56, Gabriele Fatigati a écrit : > Hi Brice, hi Jeff, > > >Can you add some printf inside hwloc_linux_set_area_membind() in > src/topology-linux.c to see if ENOMEM comes from the mbind >syscall or > not? > > I added printf inside that function, but ENOMEM does not come from there.

Re: [hwloc-users] Thread binding problem

we're talking about 1,6MB only here. So there's still something else eating all the memory. /proc/meminfo (MemFree) and numactl -H should again help. Brice > > > > 2012/9/6 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > Le 06/09/2012 1

Re: [hwloc-users] Solaris and hwloc

Le 13/09/2012 00:26, Jeff Squyres a écrit : > On Sep 12, 2012, at 10:30 AM, Samuel Thibault wrote: > >>> Sidenote: if hwloc-bind fails to bind, should we still launch the child >>> process? >> Well, it's up to you to decide :) > > Anyone have an opinion? I'm 60/40 in favor of not letting it run,

Re: [hwloc-users] Solaris and hwloc

If the user really wants something to > run without binding, then you can just do that in the shell: > > - > hwloc-bind ...whatever... my_executable > if test "$?" != "0"; then > # run without binding > my_executable > fi > - > > My

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

Le 03/10/2012 17:23, Sebastian Kuzminsky a écrit : > On Tue, Oct 2, 2012 at 5:14 PM, Samuel Thibault > > wrote: > > There were two bugs which resulted into cpuid not being properly > compiled. I have fixed them in the trunk, could

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

Le 25/10/2012 23:42, Samuel Thibault a écrit : > 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

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

Le 25/10/2012 23:57, Robin Scher a écrit : > On OS-X, you can get this string from the sysctlbyname() call: > > const char *name = "machdep.cpu.brand_string"; > char buffer[ 64 ]; > size_t size = 64; > if( !sysctlbyname( name, buffer, , NULL, 0 ) ) > memcpy( cpu_model,

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

int the number of sockets. of > http://www.open-mpi.org/projects/hwloc/doc/v1.5.1/ > ] > I see objects type 1,2,4 and 6 only. > > So, will there be another (non socket hwloc object based) way to get > CPUModel or will it find sockets as on Linux ? > > Thanks. > > Olivier Ce

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

Le 02/11/2012 21:03, Brock Palen a écrit : > This isn't a hwloc problem exactly, but maybe you can shed some insight. > > We have some 4 socket 10 core = 40 core nodes, HT off: > > depth 0: 1 Machine (type #1) > depth 1: 4 NUMANodes (type #2) > depth 2:4 Sockets (type #3) >

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

Le 02/11/2012 21:22, Brice Goglin a écrit : > hwloc-bind --get-last-cpu-location --pid should give the same > info but it seems broken on my machine right now, going to debug. Actually, that works fine once you try it on a non-multithreaded program that uses all cores :) So you can u

[hwloc-users] hwloc@SC12

Hello, If you're attending SC12, feel free to come to the Inria booth (#1209) and say hello. Samuel and I will be there, happy to meet people in real life. Brice

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

Thanks, that was an old bug on a somehow rare XML case on a NUIOA machine. Looks like adding new test cases is indeed useful :) Brice Le 15/11/2012 13:14, Samuel Thibault a écrit : > Hello, > > Brice Goglin, le Tue 13 Nov 2012 13:45:28 +0100, a écrit : >> The Hardware Locali

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

Le 26/10/2012 09:39, Brice Goglin a écrit : > Le 26/10/2012 05:22, Robin Scher a écrit : >> I would love to get this by my next release, say in the next 3-6 >> months. Is that something that would be possible? Is there anything I >> can do to help? > > We'll have a

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

Le 19/11/2012 21:01, Andrew Somorjai a écrit : > Below I posted a simple windows thread creation C++ routine which sets > the processor affinity to two cores. > What I want is the equivalent code using hwloc. Sorry for being > somewhat new to this but I'm not sure what > api calls are equivalent

Re: [hwloc-users] GPU devices appear as PCI devices

Ask nvidia to make their cuda driver free, and to add them to sysfs :) There's a cuda hwloc branch that will solve this. In the meantime, there are no nvidia osdevs. Maybe look at hwloc/cuda.h and cudart.h, they give cuda device affinity without osdevs. Brice Guillermo Miranda

Re: [hwloc-users] "-lnuma" missing from pkg-config information?

Hello Erik I am not a pkgconfig expert but my feeling is that this has buggy for a long time. hwloc.pc.in should likely use HWLOC_LIBS instead of LIBS. On my machine, it makes Libs.private change from -dl to -lm -lnuma here (with -lpci -lxml2 depending on the config). We also need to check whether

Re: [hwloc-users] hwloc on Blue Gene/Q?

Hello Erik, We need specific BGQ binding support, the binding API is different. Also we don't properly detect the 16 4-way cores properly, we only only 64 identical PUs. I am supposed to get a BGQ account in the near future so I hope I will have everything working in v1.7. Stay tuned Brice Le

Re: [hwloc-users] Mapping a GPU to a pci local CPU on Windows

Is your machine NUMA? Maybe Windows returns an error when requesting numa info on non-NUMA info? Brice Le 08/01/2013 18:44, Ashley Reid a écrit : > OS says DEVPKEY_Numa_Proximity_Domain does not exist. Neither does > DEVPKEY_Device_Numa_Node . For all devices. > > Lame :/ > > Thanks, > Ash >

Re: [hwloc-users] Segmentation fault in collect_proc_cpuset, topology.c line 1074

Hello Indeed, there's a big cgroup crash in 1.6. Can you verify that 1.6.1rc2 works fine? Thanks Brice cesse...@free.fr a écrit : >Hello, > >When updating from 1.5.1 to 1.6 I get a segfault when inside a >cgroup/cpuset in collect_proc_cpuset, file topology.c line 1074. > >It appears that an

Re: [hwloc-users] hwloc-1.6.1rc2 Build failure with Cray compiler

Did this work in the past? I don't think we changed this code recently. Can you run "make check" to make sure this change doesn't break anything? Thanks Brice Le 17/01/2013 19:19, Erik Schnetter a écrit : > hwloc-1.6.1rc2 fails to build with the Cray compiler > > Cray C : Version 8.1.2 Thu Jan

Re: [hwloc-users] hwloc-1.6.1rc2 Build failure with Cray compiler

Does Cray fix such bugs quickly usually? If so, no need to change hwloc. If not, I'll need somebody to test the change on other cray platforms and compiler versions. Brice Jeff Hammond a écrit : >This is a bug in the Cray compiler. They cannot and should not set >the

Re: [hwloc-users] OpenGL GPU detection code

Le 29/01/2013 10:14, Stefan Eilemann a écrit : > Hi, > > On 29. Jan 2013, at 8:13, Brice Goglin <brice.gog...@inria.fr> wrote: > > [snip] >> Could you send a diff against this branch instead? > I missed this branch. I'll merge this into the current implementation and

Re: [hwloc-users] OpenGL GPU detection code

gt; Sent: Tuesday, January 29, 2013 7:46 AM > To: Brice Goglin > Cc: Hardware locality user list > Subject: Re: [hwloc-users] OpenGL GPU detection code > > Hi Brice, > > On 29. Jan 2013, at 15:25, Brice Goglin <brice.gog...@inria.fr> wrote: > >> FWIW, I finally mana

Re: [hwloc-users] OpenGL GPU detection code

I just committed big changes to the display branch (and I also merged latest trunk changes). lstopo will now report things like this: PCI 10de:06d1 GPU L#0 ":0.0" GPU L#1 "cuda0" GPU L#2 "nvml0" The changes include: 1) We don't have a "display" specific OS

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

Le 07/02/2013 18:48, Eugene Loh a écrit : > I'm attaching a patch. Thanks a lot Eugene. I've tested that and it looks OK to me. I am committing it, it will be in v1.7 and v1.6.2. I guess now you want Jeff to include r5295 in OMPI. Brice

Re: [hwloc-users] hwloc on Blue Gene/Q?

nal 6 (SIGABRT) in a routine > called ".raise". > > I'd be happy to help debug this. How? > > -erik > > > > > On Sat, Feb 9, 2013 at 5:46 PM, Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> wrote: > > The new "bg

Re: [hwloc-users] Zero cache line size on Power7?

I think I've seen cases where the device-tree contains 0 for such line sizes. I guess we should document that the line size is 0 means unknown. Can you send the tarball generated by hwloc-gather-topology ? (send it only to, in a private email) Brice Le 27/02/2013 23:11, Erik Schnetter a écrit

Re: [hwloc-users] Zero cache line size on Power7?

gt; No tarball is generated. > > -erik > > > > On Wed, Feb 27, 2013 at 5:19 PM, Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> wrote: > > I think I've seen cases where the device-tree contains 0 for such > line sizes. >

Re: [hwloc-users] Many queries creating slow performance

Hello Simon, I don't think anybody every benchmarked this, but people have been complaining this problem appearing on large machines at some point. I have a large SGI machine at work, I'll see if I can reproduce this. One solution is to export the topology to XML once and then have all your MPI

Re: [hwloc-users] Trying to get last cpu location

unning on cpuset %s\n", str); > free(str); > > hwloc_cpuset_from_nodeset(topology, cpuset, nodeset); > if( hwloc_set_membind_nodeset(topology, nodeset, HWLOC_MEMBIND_BIND, > HWLOC_MEMBIND_THREAD) < 0 ) > abort(); > > ... > > I omitted som

Re: [hwloc-users] Many queries creating slow performance

Just tested on a 96-core shared-memory machine. Running OpenMPI 1.6 mpiexec lstopo, here's the execution time (mpiexec launch time is 0.2-0.4s) 1 rank : 0.2s 8 ranks: 0.3-0.5s depending on binding (packed or scatter) 24ranks: 0.8-3.7s depending on binding 48ranks: 2.8-8.0s depending on

Re: [hwloc-users] [EXTERNAL] Re: Many queries creating slow performance

H i.e. Hydra, then I'm sure Intel will be > committed to helping fix it since Intel MPI is using Hydra as the > launcher on systems like Stampede. > > Best, > > Jeff > > On Tue, Mar 5, 2013 at 3:05 PM, Brice Goglin <brice.gog...@inria.fr> > wrote: > > Just te

Re: [hwloc-users] Windows binaries miss lib file

Thanks, there was indeed an issue on the machine that builds the Windows zipballs. I am fixing this. Should be fixed in 1.7.1. If anybody needs updated earlier Windows zipballs, please let me know. Brice Le 20/05/2013 14:19, Hartmut Kaiser a écrit : > Hey all, > > The V1.7 (and V1.7.1-rc1)

Re: [hwloc-users] Windows binaries miss lib file

now. All earlier releases (except v0.9) were already OK. Final v1.7.1 expected today or wednesday. Brice Le 20/05/2013 18:45, Brice Goglin a écrit : > Thanks, there was indeed an issue on the machine that builds the Windows > zipballs. I am fixing this. Should be fixed in 1.7.1. If a

Re: [hwloc-users] hwloc on Xeon Phi

Le 18/06/2013 08:52, pinak panigrahi a écrit : > Hi, how do I use hwloc on Intel Xeon Phi. I have written codes that > use it for Sandybridge. Hello, If you really mean 'inside the Xeon Phi", it should just work and report all available Phi cores. If you mean managing the Phi internal topology

Re: [hwloc-users] Open-mpi + hwloc ...

Hello, hwloc can only tell where CPU/device are, and place programs on the right CPUs. hwloc isn't going to convert your parallel program into a GPU program. If you want to use NVIDIA GPUs, you have to rewrite your program using CUDA, OpenCL, or a high-level heterogeneous langage. Brice Le

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

put in 1.7.2 ? (see also my other email I sent to > you 2 minutes ago). > > Jirka > > > > > On Thu, Aug 29, 2013 at 11:32 AM, Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> wrote: > > The Hardware Locality (hwloc) te

Re: [hwloc-users] CPU binding

Le 03/10/2013 02:56, Panos Labropoulos a écrit : > Hallo, > > > I initially posted this at us...@open-mpi.org . > > We seem to be unable to to set the cpu binding on a cluster consisting > of Dell M420/M610 systems: > > [jallan@hpc21 ~]$ cat report-bindings.sh #!/bin/sh

Re: [hwloc-users] [WARNING: A/V UNSCANNABLE]Re: [OMPI users] SIGSEGV in opal_hwlock152_hwlock_bitmap_or.A // Bug in 'hwlock" ?

losed". Brice Le 04/11/2013 22:33, Paul Kapinos a écrit : > Hello again, > I'm not allowed to publish to Hardware locality user list so I omit it > now. > > On 11/04/13 14:19, Brice Goglin wrote: >> Le 04/11/2013 11:44, Paul Kapinos a écrit : >>> Hello all, >>&

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

index1 object:index2 is easy to write, I'd vote for not making the code too complex. Brice > > Thanks a lot! > Jirka > > > On Wed, Nov 6, 2013 at 3:06 PM, Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> wrote: > > The Hardware Locality

Re: [hwloc-users] DELL 8 core machine + Quadro K5000 GPU Card...

Le 18/11/2013 02:14, Solibakke Per Bjarte a écrit : > Hello > > I recently got access to a very interesting and powerful machine: Dell > 8 core + GPU Quadro K5000 (96 cores). > A total of 1536 cores in the original machine configuration. Hello GPU cores are not real cores so I am not sure your

Re: [hwloc-users] Regarding the Dell 8 core machine with GPUs

't contain the kernel version ("uname -a" would be more useful) but I don't need this information anymore anyway. Looks like I am ready to release the final hwloc v1.8 now :) Brice Le 18/11/2013 04:17, Solibakke Per Bjarte a écrit : > Dear Brice Goglin > > Sorry, there mus

Re: [hwloc-users] windows PCI locality (was; DELL 8 core machine + Quadro K5000 GPU Card...)

data[0] = 0; > > DEVPROPTYPE type; > > DEVPROPKEY key = DEVPKEY_Numa_Proximity_Domain; > > > > lastError = 0; > > > > ret = SetupDiGetDeviceProperty(hNvDevInfo, > , , , (PBYTE)[0], 20*sizeof(int), NULL

  1   2   3   >