Dear Dick,
A couple of suggestions re your
proposal:
- If ASSERTIONS is put at the end of the
MPI_INIT_ASSERTED argument list, in C++ one can declare the last argument as
having a zero default value, and skip
it if necessary. This might help with deprecation of the earlier MPI_INIT_*
calls.
- In non-Cray parts of the world, an MPI_INT followed
by MPI_FLOAT is likely to be a 4-byte int followed by a 4-byte float. This sometimes depends on the compiler settings in
effect, too.
- I don't think MPI_NO_THREAD_CONTENTION is really
necessary. The original thread level
settings, in particular, the use of anything but
MPI_THREAD_MULTIPLE, seem to capture the semantics that you
proposed.
- I can't fully follow the motivation for
MPI_NO_ANY_SOURCE deprioritization. AFAIK, a rendezvous exchange usually starts
with a ready-to-send packet that contains the size of the message. In this
case the receiving side will normally reply with a ready-to-receive
regardless of the buffer space available, and flag MPI_ERR_TRUNCATED on message
arrival if necessary. In this case, neither
MPI_ANY_SOURCE not MPI_NO_ANY_SOURCE seem to get into
way.
Best regards.
Alexander
From: Supalov, Alexander
Sent:
Friday, June 20, 2008 8:29 AM
To: 'MPI 3.0 Sub-setting working
group'
Subject: RE: [Mpi3-subsetting] MPI subsetting: charting the way
forward at atelecon next week?
Dear Dick,
Thank you. I remember we exchanged a couple of emails about
the possible extensions to the set of assertions, like one-sided and I/O, and in
my recollection, almost reached an agreement that this can improve performance
and possibly memory footprint, as well as be expressed thru assertions. Do you
still feel favorable about this?
Best regards.
Alexander
Hello to the Subset WG
I appreciate the interest in my proposal for
Init time assertions. Unfortunately I will not be able to come to the next Forum
meeting to discuss face to face.
I did write up a fairly detailed draft a
few weeks back and post it on the MPI 2.2 Wiki at: http://svn.mpi-forum.org/trac/mpi-forum-web/wiki/InitTimeAssertions
Maybe
that will help clarify what I have in mind. My proposal does not include "hints"
so I did not discuss the definition of a hint. I did try to be firm about the
meaning of an assertion.
Dick Treumann
Dick Treumann - MPI
Team/TCEM
IBM Systems & Technology Group
Dept 0lva / MS P963 -- 2455
South Road -- Poughkeepsie, NY 12601
Tele (845) 433-7846 Fax (845)
433-8363
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.