pi.org<mailto:hwloc-users@lists.open-mpi.org>
https://lists.open-mpi.org/mailman/listinfo/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
___
hwloc-users mailing list
hwloc-users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/hwloc-users
loc-users mailing list
> hwloc-users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
___
hwloc-users mailing list
hwloc-users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-users
ailable under
https://www.open-mpi.org/community/lists/ (so that we don't break lots of old
links from around the web), but they are frozen. No new messages have been
added to the frozen archive since late July 2016 or so.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go
e to work). We will
eventually remove links to this archive from the Open MPI web site, and replace
them with links to the new Mail Archive. Hopefully, the old archive will
eventually disappear from Google, and will effectively be replaced by the new
copies of the same mails at mail-archive.com.
--
...and we're back.
NOTE: the email address for this list has now changed! It is now
@lists.open-mpi.org (it used to be @open-mpi.org).
PLEASE UPDATE YOUR CONTACTS AND MAIL CLIENT FILTERS!
> On Jul 27, 2016, at 12:01 PM, Jeff Squyres (jsquyres)
> wrote:
>
> We are b
We unfortunately ran into major issues while trying to migrate these lists, and
have therefore restored them back on the Indiana U servers until we try the
migration again.
Sorry for the hassle folks; stay tuned!
> On Jul 20, 2016, at 10:28 AM, Jeff Squyres (jsquyres)
> wrote:
>
We are beginning the list migration process; this list will be suspended while
it is in transit to a new home.
We can't predict the exact timing of the migration -- hopefully it'll only take
a few hours.
See you on the other side!
--
Jeff Squyres
jsquy...@cisco.com
For corpo
l continue to be available,
but they'll be frozen -- no new messages will be added there. Specifically:
links to old posts will continue to work.
2. New web archives for all the lists -- to include all the old posts -- will
become available elsewhere. Specifics will be included in
oc-users mailing list
> hwloc-us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
> Link to this post:
> http://www.open-mpi.org/community/lists/hwloc-users/2015/04/1163.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
, 2014, Samuel Thibault
> wrote:
> 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
e
>
> (write 1 instead of 0 to reenable them).
But keep in mind that this is the semantic equivalent of using hwloc-bind to
bind to the first HT in each core.
I.e., disabling HT in the Linux kernel just disables scheduling on the 2nd HT.
--
Jeff Squyres
jsquy...@cisco.com
For corporate l
ou can run dozens on web server VMs on a machine with 10 cores.
Each VM will say that it has, say, 1 or 2 cores. But clearly, the sum of
number of cores in the VMs is larger than the total number of physical cores.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal informatio
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
> Link to this post:
> http://www.open-mpi.org/community/lists/hwloc-users/2014/12/1126.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
fic about what information you want to query?
I ask because it strikes me that hwloc does gather some kinds of hardware
information and put them as attributes on existing hwloc topology objects.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ada-370
> Revision:
> Serial:
>
> thanks
> Brice
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
stopo: topology-linux.c:2731: look_sysfsnode: Assertion `node == res_obj'
failed.
Aborted (core dumped)
In 1.8, the issue is the same, but a different line number (2741).
It's an SGI x86_64 server, running SLES 11.
Is this an hwloc issue, or a hardware issue?
--
Jeff Squyres
jsquy..
pk224850@linuxitvc00:~/SVN/mpifasttest/trunk[511]lstopo 1.5
>>>> $ lstopo lstopo_linuxitvc00_1.5.txt
>>>> $ lstopo lstopo_linuxitvc00_1.5.xml
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 11/01/13 15:37, Brice G
hen (Germany)
> Tel: +49 241/80-24915
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
[cid:2e96120b-7548-4e23-9f50-876178585eff@emea.cisco.com]
it until the migration is done.
Please let me know if you have any questions or issues about this migration.
Regards,
--
- DongInn
---
CREST System administrator
Indiana University
Bloomington, IN
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
For
r Architectures
>> Sandia National Laboratories, NM
>>
>>
>>
>>
>>
>>
>> ___
>> hwloc-users mailing list
>>
>> hwloc-us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
parsing code is shared anyway.
I think the philosophy should apply to all executables, actually.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
thing 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 $0.02. :)
On Sep 13, 2012, at 4:09 AM, Brice Goglin wrote:
> (resending
n the situation. The binding might only be an
> optimization, and failing just because of that is not nice. When it's an
> administration decision, it's different, but then one would use cgroups
> & such instead.
How about adding a flag to make it fail if it doesn&#x
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 has lgrp support -- that should work. right?
--
Jeff Squyres
jsquy...@cisco.com
For co
nale that the user asked for something that we can't deliver, so we
shouldn't continue.
Any idea what numactl does if it can't bind?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
1 PU
at a time. I suppose we should release-note that...
(Sorry Siegmar! :-( )
And just so I understand -- we don't have lgrp support in hwloc, mainly because
no one had the cycles/interest to implement it. Is that correct?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal informa
try to test our compiler?
>
>
> Kind regards
>
> Siegmar
>
>
> ##
> # #
> # Hochschule Fulda University of Applie
ve seen cases of heap corruption lead to malloc incorrectly failing with
ENOMEM.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ati
>>
>> HPC specialist
>>
>> SuperComputing Applications and Innovation Department
>>
>> Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy
>>
>> www.cineca.itTel: +39 051 6171722
>>
>> g.fatigati [AT] cineca.it
>
>
>
>
> --
> Ing. Gabriele Fatigati
>
> HPC specialist
>
> SuperComputing Applications and Innovation Department
>
> Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy
>
> www.cineca.itTel: +39 051 6171722
>
> g.fatigati [AT] cineca.it
>
>
>
> --
> Ing. Gabriele Fatigati
>
> HPC specialist
>
> SuperComputing Applications and Innovation Department
>
> Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy
>
> www.cineca.itTel: +39 051 6171722
>
> g.fatigati [AT] cineca.it
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
fo --pid
> is _wonderful_
>
> I think I am good to go.
>
> Brock Palen
> www.umich.edu/~brockp
> CAEN Advanced Computing
> bro...@umich.edu
> (734)936-1985
>
>
>
> On Aug 10, 2012, at 5:14 PM, Jeff Squyres wrote:
>
>> I don't know why Google is p
mich.edu
> (734)936-1985
>
>
>
> On Aug 10, 2012, at 4:26 PM, Jeff Squyres wrote:
>
>> Try looking here:
>>
>> http://www.open-mpi.org/projects/hwloc/doc/
>>
>> You have an extra "projects" in your URL. How did you get to that URL? Do
/doc/
>
> Oh noooss!!!
>
> Brock Palen
> www.umich.edu/~brockp
> CAEN Advanced Computing
> bro...@umich.edu
> (734)936-1985
>
>
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://ww
bsite is not really felpful, it talks about 4-16
> cores for the DL165 G7, while you have 24.
How old is your Dell BIOS firmware? You might need to update it.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
iendly, and make it the same (as much
as possible) between 1.6.x and 1.7.x. I'll work on that.
On May 30, 2012, at 10:06 AM, Brice Goglin wrote:
> Jeff,
> What is the displayed bitmask in OMPI 1.6? Is it the hwloc bitmask? Or
> the OMPI bitmask made of OMPI indexes?
> Brice
>
&g
OMPI binding options to understand what it was supposed to do in your case.
>
> Brice
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
; I just felt the need to share this story :-) )
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
svbu-mpi058.pdf
Description: Adobe PDF document
svbu-mpi059.pdf
Description: Adobe PDF document
iirc).
Ok. But in terms of walking down the hwloc tree, PCI devices will show up in
someone's children[] array, right? I.e., they're not in a separate list
somewhere, right?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
When PCI devices are put into the tree, do they potentially make other objects
be a different depths?
For example, http://www.open-mpi.org/projects/hwloc/devel09-pci.png has a PCI
bridge hanging off a socket. Are the cores on sockets P0 and P1 at the same
depth?
--
Jeff Squyres
jsquy
ent, I think you want --enable-static (and possibly
--disable-shared).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ve):
Probe / display PCI devices: yes
Graphical output (Cairo):yes
XML input / output: full
Memory support: binding, set policy, migrate pages
---------
--
Jeff Squyres
jsquy...@cisco.com
For corpor
full
Memory support: none
-
XML support will show "basic" if libxml2 is not found.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
pen-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Nov 29, 2011, at 10:33 AM, Brice Goglin wrote:
>> - Kerrighard
>> - PCI device support
>> - XML support
>
> I would put XML, PCI, Cairo and libnuma
What about MX, verbs, Cuda, ...?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http:/
very
> concise list at the end (Supported: A B C\n Unsupported: D E F).
Let me throw this back to Brice / Samuel...
If we had such a thing at the bottom of configure, what items should we show?
I can think of the following obvious ones offhand:
- Kerrighard
- PCI device support
- XML support
ikely got
at least *some* experience and it shouldn't be unreasonable to ask you to go
look in the output of configure.
Don't get me wrong -- I'm not dead-set against a listing at the bottom. I just
find it redundant and somewhat of a maintenance hassle.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
e to agree that a shell script similar to what Brice typed might be
much easier.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ics are
> printed.
>
> How can I tell HWLOC to look for those two machines ?
>
>
>
> --
>
> Seb
>
>
>
> _______
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Woo hoo! Brice, Samuel, and I wrote an article about hwloc for Linux Pro
Magazine. My copy just showed up in the mail:
http://blogs.cisco.com/performance/hwloc-article-published-in-linux-pro-magazine/
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http
identical environment. That viewpoint
> may or may not be shared by the OMPI developers.
>
> -Dave
>
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwl
e to pass the --disable-gcc-builtin from
> the main configure, right (since we pull in config/hwloc_internal.m4)?
> So we would pass it similar to how we had to pass --disable-xml to
> turn off that feature in the builtin hwloc (before it was turned off
> by default).
>
> -- Josh
>
rsey
> Postdoctoral Research Associate
> Oak Ridge National Laboratory
> http://users.nccs.gov/~jjhursey
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ory
>
>
> Can anyone please help me as to what is the reason for this error and where
> can I find this shared
> library.
>
> Thanks.
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/ma
Maybe this is an OS or envrionment
> specific
> problem, but at least here on FreeBSD the new memory is not zero-ed out and
> POSIX doesn't require realloc to do that.
>
> This report is for the version 1.1.2.
> Apologies for the noise if this problem is already fixed
e release 1.5.2rc1 today. It contains the hwloc stuff.
> I appreciate the hard work of the OMPI team, and am look forward to a more
> flexible binding option in OMPI's future release.
Thanks! We're shooting for 1.5.3, but it might slip to 1.5.4.
--
Jeff Squyres
jsquy...@cisc
direction led me to
> hwloc-bind.
>
> Maybe I should bring the issue of rankfile + appfile to the OMPI mailing list.
Yes.
I'd have to look at it more closely, but it's possible that we only allow one
rankfile per job -- i.e., that the rankfile should specify all the procs
.sh is:
-
#!/bin/sh
if test "$OMPI_COMM_WORLD_RANK" = "0"; then
bind_string=...whatever...
else
bind_string=...whatever...
fi
hwloc-bind $bind_string $*
-
Something like that.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
eans next week, you should know
> that hwloc will be there too. I will be hanging around the INRIA Booth
> (#2751, between TACC and Microsoft) and Jeff Squyres will be near the
> Cisco Booth (#3247, on the other side of Microsoft). Feel free to visit
> us and re
ndex file error: Could
> not open the index file './index.swish-e': No such file or directory
Ouch! I'll get that fixed... Thanks for letting us know.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
>
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Jun 23, 2010, at 4:29 PM, Brice Goglin wrote:
> Don't you want hwloc_cpuset_set(set, i) instead ?
> hwloc_cpuset_cpu(set, i) changes the cpuset into a single CPU, i.e. it's
> zero(set) + set(set, i).
Ah. Well, that would do it. :-)
--
Jeff Squyres
jsquy...@cisco.com
ering | +1.650.633.7054
>> Oracle - Performance Technologies
>> 95 Network Drive, Burlington, MA 01803
>> Email terry.don...@oracle.com
>>
>>
>> ___
>> hwloc-users mailing list
>>
>> hwloc-us...@
On Jun 22, 2010, at 8:48 AM, Jirka Hladky wrote:
> So basically, until libtool patch will make through upstream into other
> distributions it will be needed to patch configure script.
Bummer. But at least it's a good explanation and a workaround!
--
Jeff Squyres
jsquy...@ci
d.
Awesome; thanks.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ady fixed.
My (double) bad -- the current released version is 1.0.1. We haven't changed
anything other than Samuels' S/LIBS/LDADD/ stuff.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
definitely not a preferred solution; I don't want to get in the
business of frobbing a generated libtool script (we do it in Open MPI to work
around esoteric bugs and it's awful awful awful).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
s from ld.so.conf (that makes sense actually). Could you post your
> /etc/ld.so.conf (and any file that it could include)?
>
> Samuel
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/li
hwloc_topology_set_xml() function.
See the output of "lstopo --help" for a specific list of what graphical
output formats are supported in your hwloc installation.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On May 17, 2010, at 11:41 AM, Jirka Hladky wrote:
> BTW, is there any time-plan for hwloc 1.0 to be released?
There were some trivial changes since rc6; I have one more trivial change to
make today and then we're probably good to go.
--
Jeff Squyres
jsquy...@cisco.com
For corpora
d it on box with more than 64 CPUs. If so, can
> you please share your results?
>
> Thanks a lot!
> Jirka
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
>
/
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
the kernel exports wrong NUMA info...
>
> Brice
>
> ___
> hwloc-users mailing list
> hwloc-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
--
Jeff Squyres
jsquy...@cisco.com
ger of the
libtopology project from INRIA and the Portable Linux Processor
Affinity (PLPA) sub-project from Open MPI. *Both of these prior
projects are now deprecated.*
--
Jeff Squyres
jsquy...@cisco.com
FYI: Because the libtopology web site will disappear someday, and
because we haven't released a version of hwloc yet, I posted the
libtopology v0.9 tarballs here:
http://www.open-mpi.org/software/hwloc/v0.9/
--
Jeff Squyres
jsquy...@cisco.com
73 matches
Mail list logo
