Re: [hwloc-users] more detailed errors

What is errno after load() failing? Brice On 17 septembre 2014 17:43:13 UTC+02:00, "Aulwes, Rob" wrote: >Hi, > >A call to hwloc_topology_load is failing, but all that is returned is >–1. Are there error reporting routines that can be called to get more >details about the error? The doc for hwlo

Re: [hwloc-users] problem with X11 using Solaris

Can you send the output of configure, the generated config.log and your unmodified Xutil.h? My solaris/openindiana doesn't have that problem. thanks Brice Le 16/09/2014 14:43, Siegmar Gross a écrit : > Hi, > > today I installed hwloc-1.9.1 on my machines (Solaris 10 Sparc (tyr), > Solaris 10 x86

Re: [hwloc-users] setting memory bindings

t_numanode_obj_by_os_index? > > Thanks,Rob > > > *From:* hwloc-users [hwloc-users-boun...@open-mpi.org] on behalf of > Brice Goglin [brice.gog...@inria.fr] > *Sent:* Thursday, September 04, 2014 6:25 AM > *To:* hwloc-us...@open-mpi.org > *Subject:* Re: [hwloc-users] setting

Re: [hwloc-users] hwloc error with "node interleaving" disabled

Don't be sorry, I used "yet another" to complain about all these buggy AMD platforms, and not to complain about their owners ;) Bug reports are always welcome, that's why the big warning says you should report it. Also these warnings vary a little bit with the platform and processor model so i

Re: [hwloc-users] hwloc error with "node interleaving" disabled

Hello You sent the test.output file instead of test.tar.bz2 so I can't check for sure. Anyway I guess this is yet another buggy AMD platform with magny-cours/interlagos/abu-dahbi Opterons (61xx, 62xx or 63xx). Sometimes upgrading the BIOS/kernel helps. Sometimes not. Some L3 caches will be missi

Re: [hwloc-users] setting memory bindings

I added a new doc/examples/ repository to better show how to use bitmaps, cpu and memory binding etc. https://github.com/open-mpi/hwloc/tree/master/doc/examples If you see anything missing, don't hesitate to ask. Brice Le 19/08/2014 19:10, Aulwes, Rob a écrit : > ok, in the meantime, is th

Re: [hwloc-users] setting memory bindings

thout the STRICT flag. And I'll see if I add a good example somewhere. Brice Le 19/08/2014 19:00, Aulwes, Rob a écrit : > nope, no error. is there a way to find out what policies are > supported? I would like to try 'replicate'. > > From: Brice Goglin mailto:brice.gog.

Re: [hwloc-users] setting memory bindings

any doc? > > Thanks for the help! Rob > > From: Brice Goglin mailto:brice.gog...@inria.fr>> > Reply-To: Hardware locality user list <mailto:hwloc-us...@open-mpi.org>> > Date: Tue, 19 Aug 2014 19:03:56 +0200 > To: Hardware locality user list <mailto:hw

Re: [hwloc-users] setting memory bindings

ould like to try 'replicate'. > > From: Brice Goglin mailto:brice.gog...@inria.fr>> > Reply-To: Hardware locality user list <mailto:hwloc-us...@open-mpi.org>> > Date: Tue, 19 Aug 2014 18:55:57 +0200 > To: Hardware locality user list <mailto:hwloc-us...

Re: [hwloc-users] setting memory bindings

* sizeof (T)); > hwloc_set_area_membind_nodeset(_topo, p, cnt * sizeof (T), > > mem_nodeset, HWLOC_MEMBIND_NEXTTOUCH, 0); > > where > > mem_nodeset = hwloc_topology_get_complete_nodeset(_topo); > > Thanks,Rob > > From: Brice Goglin

Re: [hwloc-users] setting memory bindings

Le 19/08/2014 18:38, Aulwes, Rob a écrit : > Hi, > > I'm trying to write a custom C++ allocator that wraps hwloc calls. > I've tried using various hwloc_alloc* functions to set the memory > bindings, but when I call hwloc_get_area_membind_nodeset to verify, I > don't get the same policy I passed t

Re: [hwloc-users] [WARNING: A/V UNSCANNABLE]Re: hwloc error

Le 16/08/2014 18:37, Andrej Prsa a écrit : > Hi Brice, > >> Your kernel looks recent enough, can you try upgrading your BIOS ? You >> have version 3.0b and there's a 3.5 version at >> http://www.supermicro.com/aplus/motherboard/opteron6000/sr56x0/h8qg6-f.cfm > For completeness, I just tried updatin

Re: [hwloc-users] [WARNING: A/V UNSCANNABLE] hwloc error

Le 15/08/2014 14:59, Andrej Prsa a écrit : > Hi Brice, > >> Your kernel looks recent enough, can you try upgrading your BIOS ? You >> have version 3.0b and there's a 3.5 version at >> http://www.supermicro.com/aplus/motherboard/opteron6000/sr56x0/h8qg6-f.cfm > Flashing bios is not the easiest optio

Re: [hwloc-users] [WARNING: A/V UNSCANNABLE] hwloc error

Hello, Your platform reports buggy L3 cache locality information. This is very common on AMD 62xx and 63xx platforms unfortunately. You have 8 L3 caches (one per 6-core NUMA node, two per socket), but the platform report 11 L3 caches instead: Socket s1, 2 and 4 report one L3 above 2 cores, one L3

Re: [hwloc-users] hwloc 1.9 and openmpi using intel compiler

This commit should fix it. https://github.com/open-mpi/hwloc/commit/f46c983df58a41ec8f994f30f57154bd78392de8.patch Brice Le 09/07/2014 23:42, Nick Papior Andersen a écrit : > Dear Brice > > > 2014-07-09 21:34 GMT+00:00 Brice Goglin <mailto:brice.gog...@inria.fr>>: > &

Re: [hwloc-users] hwloc 1.9 and openmpi using intel compiler

4 23:42, Nick Papior Andersen a écrit : > Dear Brice > > > 2014-07-09 21:34 GMT+00:00 Brice Goglin <mailto:brice.gog...@inria.fr>>: > > Le 09/07/2014 23:30, Nick Papior Andersen a écrit : >> Dear Brice >> >> Here are my findings (apologies for not

Re: [hwloc-users] hwloc 1.9 and openmpi using intel compiler

Le 09/07/2014 23:30, Nick Papior Andersen a écrit : > Dear Brice > > Here are my findings (apologies for not doing make check on before-hand!) > > 2014-07-09 20:42 GMT+00:00 Brice Goglin <mailto:brice.gog...@inria.fr>>: > > Hello, > > A quick look in Op

Re: [hwloc-users] hwloc 1.9 and openmpi using intel compiler

Hello, A quick look in Open MPI source code seems to say that it's manipulating XML topologies in these lines. Please go into your hwloc-1.9 build directory, and run "tests/xmlbuffer" (you will may have to build it with run "make xmlbuffer -C tests"). If it works, try running "make check". Also

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

amples of 6348 (all characteristics are same). > > > On Tue, Apr 1, 2014 at 6:59 PM, Yury Vorobyov <mailto:teupol...@gmail.com>> wrote: > > The BIOS has latest version. If I should check some BIOS > information, I have access to hardware. Tell me wh

Re: [hwloc-users] divide by zero error?

gt; > Thanks, > > Andrew > >> -Original Message- >> From: Brice Goglin [mailto:brice.gog...@inria.fr] >> Sent: Monday, May 5, 2014 1:03 PM >> To: Friedley, Andrew >> Subject: Re: [hwloc-users] divide by zero error? >> >> Thanks. >&

Re: [hwloc-users] node configuration differs form hardware

Le 28/05/2014 15:46, Craig Kapfer a écrit : > Wait, I'm sorry, I must be missing something, please bear with me! > > By the way, your discussion of groups 1 and 2 below is wrong. > Group 2 doesn't say that NUMA node == socket, and it doesn't > report 8 sockets of 8 cores each. It report

Re: [hwloc-users] node configuration differs form hardware

Le 28/05/2014 14:57, Craig Kapfer a écrit : > > > Hmm ... the slurm config defines that all nodes have 4 sockets with 16 > cores per socket (which corresponds to the hardware--all nodes are the > same). Slurm node config is as follows: > > NodeName=n[001-008] RealMemory=258452 Sockets=4 CoresPerS

Re: [hwloc-users] node configuration differs form hardware

> Thanks much, > > Craig > > > On Wednesday, May 28, 2014 1:39 PM, Brice Goglin > wrote: > > > Aside of the BIOS config, are you sure that you have the exact same > BIOS *version* in each node? (can check in /sys/class/dmi/id/bios_*) > Same Linux kernel too? &g

Re: [hwloc-users] node configuration differs form hardware

Aside of the BIOS config, are you sure that you have the exact same BIOS *version* in each node? (can check in /sys/class/dmi/id/bios_*) Same Linux kernel too? Also, recently we've seen somebody fix such problems by unplugging and replugging some CPUs on the motherboard. Seems crazy but it happene

Re: [hwloc-users] divide by zero error?

Please run "hwloc-gather-topology simics" and send the resulting simics.tar.bz2 that it will create. However, I assume that the simulator returns buggy x86 cpuid information, so we'll see if we want/can easily workaround the bug or just let simics developers fix it. Brice Le 29/04/2014 01:15, Fri

Re: [hwloc-users] problem with open mpi

Hello, This list is for hwloc users (hwloc is a Open MPI subproject). You likely want Open MPI users instead: us...@open-mpi.org Brice Le 16/04/2014 18:44, flavienne sayou a écrit : > Hello, > I am Flavienne and I am a master student. > I wrote a script which have to backup sequentials applicatio

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

has latest version. If I should check some BIOS information, > I have access to hardware. Tell me what variables from SMBIOS you want > to see? > > > On Fri, Jan 31, 2014 at 1:07 PM, Brice Goglin <mailto:brice.gog...@inria.fr>> wrote: > > Hello, > > Your BI

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

oc-gui package) is still much > lower compared to lstopo-no-graphics > B) Compile it without libXNVCtrl but it will reduce the functionality. > > Is there any 3rd option? I guess not. It seems like A) is the best > choice for Fedora. > > Any ideas on that? > > Thanks!

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

Le 01/04/2014 10:43, Jiri Hladky a écrit : > Hi Brice, > > I see some compiler warnings when building rpm package for Fedora: > > topology-windows.c: In function 'hwloc_win_get_VirtualAllocExNumaProc': > topology-windows.c:338:30: warning: assignment from incompatible > pointer type [enabled by def

Re: [hwloc-users] distributing across cores with hwloc-distrib

gt; > On Sun, Mar 30, 2014 at 05:32:38PM +0200, Brice Goglin wrote: >> Don't worry, binding multithreaded processes is not a corner case. I was >> rather talking about the general "distributing less processes than there >> are object and returning cpusets as large as po

Re: [hwloc-users] distributing across cores with hwloc-distrib

hat this is considered a corner case. Could you > please consider fixing this? > > Thanks, > Tim > > Brice Goglin wrote: >> Hello, >> >> This is the main corner case of hwloc-distrib. It can return objects >> only, not groups of objects. The distrib algorit

Re: [hwloc-users] distributing across cores with hwloc-distrib

Hello, This is the main corner case of hwloc-distrib. It can return objects only, not groups of objects. The distrib algorithms is: 1) start at the root, where there are M children, and you have to distribute N processes 2) if there are no children, or if N is 1, return the entire object 3) split

Re: [hwloc-users] BGQ question.

Le 26/03/2014 01:00, Christopher Samuel a écrit : > On 26/03/14 01:34, Biddiscombe, John A. wrote: > > > If I compile on the login node, but run lstopo on the ION, I get > > this (wrong, below) > > If you build this with GCC (the standard system one, not the > cross-compiler for BGQ) does it still

Re: [hwloc-users] BGQ question.

ere we > are trying to customise the IO. > > > > JB > > > > *From:*Brice Goglin [mailto:brice.gog...@inria.fr] > *Sent:* 25 March 2014 08:43 > *To:* Hardware locality user list; Biddiscombe, John A. > *Subject:* Re: [hwloc-users] BGQ question. > > &

Re: [hwloc-users] BGQ question.

x=/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/hwloc-1.8.1 > >should I rerun with something set? > >Thanks > >JB > > >From: hwloc-users [mailto:hwloc-users-boun...@open-mpi.org] On Behalf >Of Brice Goglin >Sent: 25 March 2014 08:04 >To: Hardware locality user list &g

Re: [hwloc-users] BGQ question.

Le 25/03/2014 07:51, Biddiscombe, John A. a écrit : > > I'm compiling hwloc using clang (bgclang++11 from ANL) to run on IO > nodes af a BGQ. It seems to have compiled ok, and when I run lstopo, I > get an output like this (below), which looks reasonable, but there are > 15 sockets instead of 16. I

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

Le 13/02/2014 22:25, Jiri Hladky a écrit : > Hi Brice, > > when compiling hwloc-1.8.1 I have seen these warnings. Could you > please check them? fread() warnings come from fread() on kernel sysfs files, so it's very unlikely that we read totally buggy data from there. One day we'll fix this, maybe

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

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. Brice > > Brock P

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

r following the PCI bus order? We may want to talk to NVIDIA to get a clarification about all this. Brice > > Brock Palen > www.umich.edu/~brockp > CAEN Advanced Computing > XSEDE Campus Champion > bro...@umich.edu > (734)936-1985 > > > > On Feb 5, 2014, at 1:19 A

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

Hello Brock, Some people reported the same issue in the past and that's why we added the "nvml" objects. CUDA reorders devices by "performance". Batch-schedulers are somehow supposed to use "nvml" for managing GPUs without actually using them with CUDA directly. And the "nvml" order is the "normal

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

Hello, Your BIOS reports invalid L3 cache information. On these processors, the L3 is shared by 6 cores, it covers 6 cores of an entire half-socket NUMA node. But the BIOS says that some L3 are shared between 4 cores, others by 6 cores. And worse it says that some L3 is shared by some cores from a

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

en-mpi.org/community/lists/hwloc-devel/2014/01/4043.php Le 29/01/2014 06:50, Robin Scher a écrit : > Hi Brice > > This works great now. Thank you for your help! > -robin > > Robin Scher > ro...@uberware.net > +1 (213) 448-0443 > > > > On Jan 28, 2014, at 7:4

Re: [hwloc-users] Finding closest host bridge

The bridge cannot be "not connected to anything". All objects have a parent (and are a child of that parent) except the very-top root object. Theoretically, the bridge could be connected anywhere. In practice it's connected to a NUMA node, a root object, or (rarely) a group of numa nodes. The prob

Re: [hwloc-users] CPU info on ARM

models executing in the same SMP system)." >> >> He passed the question on to another ARM guy, asking for further detail. >> I'll pass on what he says. >> >> >> >> On Jan 28, 2014, at 3:39 AM, Brice Goglin wrote: >> >>> Hello,

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

Le 28/01/2014 14:31, Brice Goglin a écrit : > Le 28/01/2014 13:00, Samuel Thibault a écrit : >> 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,

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

Le 28/01/2014 13:00, Samuel Thibault a écrit : > 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. >> >> S

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

Le 28/01/2014 09:57, Brice Goglin a écrit : > I will debug a bit more to see if it's actually a 64bit cpuid problem > on windows. The x86 backend is entirely disabled in the 64bit windows build because configure fails to compile the cpuid assembly (in my mingw64 with gcc 4.7). It

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

Le 28/01/2014 09:46, Robin Scher a écrit : > Hi, thanks for responding. > > The CPUModel is definitely available on this machine. A 32 bit process > on the same machine correctly finds the model name using code that > calls the cpuid inline assembly to get it, and the machine itself is a > VM runn

[hwloc-users] CPU info on ARM

Hello, Is anybody familiar with ARM CPUs? I am adding more CPU information because Intel needs more: CPUVendor=GenuineIntel CPUModel=Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz CPUModelNumber=45 CPUFamilyNumber=6 Would something similar be useful for ARM? What are the fields below from /proc/cpuinf

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

Hello, The CPUModel attribute should be only in Socket or machine/root objects. At least, that's what I documented and what I seem to see in the code. Did you actually see any other place? So it may just mean that the CPUModel is not available on your machine? Or maybe the code below is buggy som

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

Maybe try to disable some dependencies such as pci in hwloc (--disable-pci), I wouldn't be surprised if there were issues there. If that helps, please let us know what was enabled before (libpciaccess (default), or libpci/pciutils (--enable-libpci)). Brice Le 18/01/2014 07:23, Robin Scher a écr

Re: [hwloc-users] hwloc errors on program startup

Hello, Linux says socket 0 contains processors 0-7 and socket 1 contains 8-15, while NUMA node 0 contains processors 0-3+8-11 and NUMA node 1 contains processors 4-7+12-15. Given why I read about Opteron 6320 online, the problem is that NUMA 0 should be replaced with two NUMA nodes with processors

Re: [hwloc-users] hwloc problem on SGI machine

Le 11/01/2014 01:58, Chris Samuel a écrit : > On Sat, 11 Jan 2014 11:54:17 AM Chris Samuel wrote: > >> We've got both an older Altix XE cluster and a UV10 (both running RHEL) I >> can test on if it's useful? > Forgot I already had both 1.7.2 and 1.8 built for both - all fine (RHEL6.4). > This was

Re: [hwloc-users] hwloc problem on SGI machine

Le 11/01/2014 00:27, Jeff Squyres (jsquyres) a écrit : > Jeff Becker (CC'ed) reported to me a failure with hwloc 1.7.2 (in OMPI > trunk). I had him verify this with a standalone hwloc 1.7.2, and then had > him try standalone hwloc 1.8 as well -- all got the same failure. > > Here's what he's see

Re: [hwloc-users] [windows] build from source using visual studio

Brice > > Thanks, > > Eloi > > > > *From:*hwloc-users [mailto:hwloc-users-boun...@open-mpi.org] *On > Behalf Of *Brice Goglin > *Sent:* mercredi 8 janvier 2014 11:49 > *To:* hwloc-us...@open-mpi.org > *Subject:* Re: [hwloc-users] [windows] build from source usin

Re: [hwloc-users] [windows] build from source using visual studio

.625: GetProcAddress(0x07FF7E1B > [c:\windows\system32\PSAPI.DLL], "QueryWorkingSetEx") called from " > XXX\bin\LIBHWLOC-5.DLL" at address 0x000069E9419E and returned > 0x07FF7E1B2E60 by thread 1. > > 00:00:00.625: First chance exception 0xC0

Re: [hwloc-users] [windows] build from source using visual studio

I've been working on adding msvc/cmake support last year (pushed some msvc-related fixes that are at least in v1.7 and later) but I stopped at some point because there was not much interest for it, and because it's not easy to do some automatic testing. I am not sure what you mean with windows 6.x

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

Hello, On windows, set/get_cpubind() are implemented by called set/get_proc_cpubind() with GetCurrentProcess() as a 2nd argument, so your code should be doing exactly the same, and I don't see what could be going on here. Do you pass any flag in these cpubind functions ? Do you get any useful erro

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

lastError = 0; > > > > ret = SetupDiGetDeviceProperty(hNvDevInfo, > &deviceInfoData,&key , &type, (PBYTE)&data[0], 20*sizeof(int), NULL,0); > > > > if (!ret) > > { > >

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

in lstopo). cpuinfo.txt doesn'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 Br

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

This seems unrelated since he seems to be running Linux anyway. We got that information a while ago but I couldn't do anything with it because (I think) I didn't have access to a Windows release that supported this. And, bigger problem, I don't have access to a Windows machine with more than one s

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] [hwloc-announce] Hardware locality (hwloc) v1.8rc1 released

only. Given that object: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 <mailto:brice.gog...@inria.fr>> wrote: > > The Hardware Locality

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

ly "closed". 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

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

o say before we get details about the crash in xmlbuffer above. Brice > > Many thanks for your help! > Best > > Paul > > pk224850@linuxitvc00:~/SVN/mpifasttest/trunk[511]lstopo 1.5 > $ lstopo lstopo_linuxitvc00_1.5.txt > $ lstopo lstopo_linuxitvc00_1.5.xml > > > &

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

Sorry, I missed the mail on OMPI-users. This hwloc looks vry old. We don't have Misc objects instead of Groups since we switched from 0.9 to 1.0. You should regenerate the XML file with a hwloc version that came out after the big bang (or better, after the asteroid killed the dinosaurs

Re: [hwloc-users] meaning of "physical CPU" for get_last_cpu_location()

Hello, The doc says "get the last physical CPU where the current process or thread ran". As usual, there's no well-defined portable way to identify those things. On AMD, it's a core. On Intel, it's a hyperthread, and could also be a core if HT is disabled. On other archs/systems, it may be called

[hwloc-users] switch to git

Dear hwloc users, As you may have noticed on the hwloc-devel list, hwloc recently switched from SVN to GIT (thanks to Jeff, Dave and DongInn for doing the actual huge work). The repository may now be checkout with git clone https://github.com/open-mpi/hwloc Trac (for tickets, changes, etc) is

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] [hwloc-announce] Hardware locality (hwloc) v1.7.2rc1 released

l output 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 <mailto:brice.gog...@inria.fr>> wrote: > > The Hardware Locality (hwloc) team is pleased to announce the first &

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 21/06

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 f

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

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

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

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

> > If this affects MPICH 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 > wrote: > > Ju

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 binding

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

oc_bitmap_asprintf(&str, cpuset); > printf("current thread running 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(); &

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 p

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

Hello Fabio, Which hwloc release are you using ? get_last_cpu_location() was only added in hwloc v1.2. It has always been available since then, even on when not supported (it will return -1 with errno=ENOSYS in this case). If this doesn't help, can you send your test program? Brice Le 05/03/2013

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

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

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] rebind subarray

Hello Rob, That's exactly what set_area_membind() was meant for. That said, you can only move entire pages (usually 4kbytes) to another domain. So you can only move half of your array if you array is larger than a single page. You likely need something like this: [... initialize the hwloc top

Re: [hwloc-users] OpenGL GPU detection code

Le 14/02/2013 20:44, Stefan Eilemann a écrit : >> Isn't it possible to have a single X server with a NVIDIA >> board driving :0.0 and a non-NVIDIA board driving :0.1 ? > Good question. I haven't seen this, so I've got no clue if one would get the > union or intersection of extensions. Maybe it's n

Re: [hwloc-users] OpenGL GPU detection code

Le 14/02/2013 14:00, Stefan Eilemann a écrit : > On 12. Feb 2013, at 23:37, Brice Goglin wrote: > >> Stefan (or anybody else interested in hwloc GPU support), >> Did you have any chance to look at this? > I can confirm that it works for us now. I did implement an imp

Re: [hwloc-users] OpenGL GPU detection code

F100 [GeForce GTX 480]") >> "nVidia Corporation GF100 [GeForce GTX 480]" >> >> >> lstopo --whole-io shows much more detail, including both sides of the >> GTX-480. >> >> I haven't yet written an OpenMPI, OpenGL program to see how it wor

Re: [hwloc-users] OpenGL GPU detection code

Stefan (or anybody else interested in hwloc GPU support), Did you have any chance to look at this? Brice Le 01/02/2013 14:57, Brice Goglin a écrit : > I just committed big changes to the display branch (and I also merged > latest trunk changes). > > lstopo will now report thin

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

ys this was signal 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 <mailto:brice.gog...@inria.fr>> wrote: > > The new "bgq" br

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

The new "bgq" branch now contains proper topology for BG/Q nodes (including cores and caches, except the prefetching cache) as well as support for set/get binding of the current thread or of another thread. No process-wide binding since I don't know how to iterate over all threads of a process. A

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] How to get the coreid of a process on which it is currently mapped?

Hello I assume you're talking about MPI ranks, right? In the general case, you can't. hwloc knows about processes, not about ranks. And there's no standard way to convert between them. That said, Open MPI defines the OMPI_COMM_WORLD_RANK environment variable that contains what you want. If you us

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] OpenGL GPU detection code

Le 29/01/2013 17:15, Stefan Eilemann a écrit : > On 29. Jan 2013, at 17:07, Brice Goglin wrote: > >> The current plan is to have some OpenCL device info and some OpenGL >> device info appear inside GPU PCI devices. That said, I am still not >> confident about the current O

Re: [hwloc-users] OpenGL GPU detection code

Eilemann > 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 wrote: > >> FWIW, I finally managed to run the c

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 wrote: > > [snip] >> Could you send a diff against this branch instead? > I missed this branch. I'll merge this into the current implementation and > ping let you

Re: [hwloc-users] OpenGL GPU detection code

Le 28/01/2013 09:53, Stefan Eilemann a écrit : > Bonjour Brice, > > we've been dragging our feet a bit to get the GPU detection code merged into > upstream, and I'm trying to get back to this now. Since we fixed a minor > issue, I've merged our changes against the current svn trunk and opened a

Re: [hwloc-users] hwloc tutorial material

Le 22/01/2013 10:27, Samuel Thibault a écrit : > 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 a

[hwloc-users] hwloc tutorial material

Hello, Despite snow storms trying to cancel all my flights, I managed to give two (basically identical) hwloc tutorials recently. A bit more than 3 hours covering a wide spectrum of features of command-line tools and of the C interface. Everything is available at http://runtime.bordeaux.inria.fr/hw

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

Le 17/01/2013 21:00, Erik Schnetter a écrit : > Given that the Cray compiler aborts on this code with an incorrect > error message, I would actually call it a compiler bug. The compiler > may possibly want to complain that it doesn't know __builtin_ffsl, but > its error message (Declaration is inco

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 __GNUC__ flag unless th

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 1

<    1   2   3   4   5   >