WHAT: Make hwloc a 1st class item in OMPI
WHY: At least 2 pieces of new functionality want/need to use the hwloc data
WHERE: Put it in ompi/hwloc
WHEN: Some time in the 1.5 series
TIMEOUT: Tues teleconf, Oct 5 (about 2 weeks from now)
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1a1r2491
Start time: Wed Sep 22 21:01:04 EDT 2010
End time: Wed Sep 22 21:03:14 EDT 2010
Your friendly daemon,
Cyrador
On Sep 22, 2010, at 4:51 PM, Ralf Wildenhues wrote:
> Thanks for the measurements! I'm a bit surprised that the speedup is
> not higher. Do you have timings as to how much of the autogen.pl time
> is spent inside automake?
No, they didn't. I re-ran them to just time autoreconf (is there a way
Hi Jeff,
adding bug-automake in Cc: (non-subscribers can't post to the Open MPI
list, so please remove that Cc: in case)
* Jeff Squyres wrote on Wed, Sep 22, 2010 at 03:50:19PM CEST:
> $AUTOMAKE_JOBS Total wall time
> valueof autogen.pl
> 8
Thank you very much.
Ken
-Original Message-
From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On Behalf
Of Jeff Squyres
Sent: Wednesday, September 22, 2010 10:09 AM
To: Open MPI Developers
Subject: Re: [OMPI devel] How to add a schedule algorithm to the pml
I see it
I see it here:
http://hal.archives-ouvertes.fr/inria-00486178/en/
On Sep 22, 2010, at 11:53 AM, Kenneth Lloyd wrote:
> Jeff,
>
> Is that EuroMPI2010 ob1 paper publicly available? I get involved in various
> NUMA partitioning/architecting studies and it seems there is not a lot of
>
Jeff Squyres, le Wed 22 Sep 2010 13:37:12 +0200, a écrit :
> I think we should support memory binding, even if it does weird things --
> i.e., dropping membinding support on a given OS shouldn't be an option.
That's why I'd tend to keep set_cpubind and set_membind, warning that
one may have
Le 22/09/2010 16:30, Jeff Squyres a écrit :
> On Sep 22, 2010, at 8:09 AM, Brice Goglin wrote:
>
>
>> hwloc_set_*? hwloc_objset* ? Anything better?
>>
>> hwloc_set_* might not be the best since we would have a hwloc_set_set()
>> function to set one bit :)
>>
> Agreed. Too bad, though -- I
On Sep 22, 2010, at 8:09 AM, Brice Goglin wrote:
> hwloc_set_*? hwloc_objset* ? Anything better?
>
> hwloc_set_* might not be the best since we would have a hwloc_set_set()
> function to set one bit :)
Agreed. Too bad, though -- I liked hwloc_set*.
hwloc_group* (that seems kinda lame, though)
Brice Goglin, le Wed 22 Sep 2010 10:38:38 +0200, a écrit :
> * Some OS bind the process too when you bind memory.
Not for all kinds of memory bindings. For now, nothing that has been
commited does that, it's only the remaining TODOs. The bindings in
question are policy binding, i.e. not binding
On Sep 21, 2010, at 12:37 PM,
wrote:
> Like I said in my earlier response, I have never tried this option. So I ran
> these tests on 1.4.2 now and apparently the behavior is same ie; the
> checkpoint creation time increases when I enable shared
I just commited the very last modifications of ROMIO (mpich2-1.3rc1)
into bitbucket.
Pascal
Jeff Squyres a écrit :
On Sep 17, 2010, at 6:36 AM, Pascal Deveze wrote:
In charge of ticket 1888 (see at
https://svn.open-mpi.org/trac/ompi/ticket/1888) ,
I have put the resulting code in
Some of you may be unaware that recent versions of automake can run in
parallel. That is, automake will run in parallel with a degree of (at most)
$AUTOMAKE_JOBS. This can speed up the execution time of autogen.pl quite a bit
on some platforms. On my cluster at cisco, here's a few quick
Thanks Lisandro!
I filed https://svn.open-mpi.org/trac/ompi/ticket/2594 about this.
On Sep 15, 2010, at 11:28 AM, Lisandro Dalcin wrote:
> I've tested this with (--enable-debug --enable-picky
> --enable-mem-debug) 1.4.2 and 1.5rc6. Despite being debug builds, a
> mpi4py user got the same with
Jeff Squyres a écrit :
On Sep 17, 2010, at 6:36 AM, Pascal Deveze wrote:
In charge of ticket 1888 (see at
https://svn.open-mpi.org/trac/ompi/ticket/1888) ,
I have put the resulting code in bitbucket at:
http://bitbucket.org/devezep/new-romio-for-openmpi/
Sweet!
The work in this
Le 22/09/2010 13:36, Jeff Squyres a écrit :
> On Sep 22, 2010, at 4:38 AM, Brice Goglin wrote:
>
>
>> There are still some problems to solve in the membind branch:
>> * Some OS bind the process too when you bind memory. I see the following
>> solutions:
>> + Add a flag such as
Sorry for the delay in replying -- I was in Europe for the past two weeks;
travel always makes me wy behind on my INBOX...
On Sep 14, 2010, at 9:56 PM, 张晶 wrote:
> I tried to add a schedule algorithm to the pml component ,ob1 etc. Poorly I
> can only find a paper named "Open MPI: A
On Sep 17, 2010, at 6:36 AM, Pascal Deveze wrote:
> In charge of ticket 1888 (see at
> https://svn.open-mpi.org/trac/ompi/ticket/1888) ,
> I have put the resulting code in bitbucket at:
> http://bitbucket.org/devezep/new-romio-for-openmpi/
Sweet!
> The work in this repo consisted in refreshing
Hello,
hwloc 1.0 was released in May. I think we should release 1.1 before
SC10, which means doing a first RC within a couple weeks.
trunk got many changes since 1.0, but nothing very important. trac says
we're missing memory binding, distances and user-defined process
restrictions. Memory
On 21/09/10 19:34, Samuel Thibault wrote:
Just a last question: is it ok to include the /proc and /sys trees you
have posted in the hwloc testcases?
That's ok.
20 matches
Mail list logo