Hi Martin, A few things... * I should probably know this, but I probably misplaced the information. How do edit the Wiki page? I tried logging in with my MPI3 Tools password, but it failed. * I think the current MPIR description on the Wiki needs a lot more detail. I think it needs to include a "C" language description that shows the declarations of the structure types, variables, and functions. It's missing type and variable declarations. At the next higher level of detail, it needs to elaborate on the semantics of each of the variables and functions, both from the debugger's and MPI perspective; it currently very thin. At the highest level of detail, it should talk about the different "modes" of useing the interface. For example, the "rank 0 process launches" model used by MPICH 1, vs. the "separate mpirun starter process launches" model used by most other MPI implementations. Also, there are special conventions and used on various MPI implementations. For example, Blue Gene (and now Open MPI) support the notion of co-spawning tool daemons, and several implementations support the notion of partial (scalable subset) attach. * On Monday, I think we need to figure out who's going to be the principle author of the document and who is going to edit/maintain the document. Cheers, John D. Martin Schulz wrote:
Hi all,
Just as a reminder: we have our next MPI Tools WG TelCon on Monday 1/12 at the usual time at 8am PT, 11am ET, 5pm MEZ. Here is the dial-in information:
Toll Free Dial In Number for Offsite Participants: 866-914-3976 International Access/Caller Paid Dial In Number: 925-424-8105 Dial In Number for LLNL Onsite Participants: 4-8105
Access Security Code: 860609 #
Unfortunately, I won't be able to be there for the whole TelCon since I will try to call-in from on the road. Bronis has agreed to lead the TelCon instead. The main topics will be to continue the discussion of the current state of the MPIR interface as well as a presentation by Chris on the MPIR-2 interface, which includes dynamic process support.
Please also take a look at the current MPIR description on the Wiki and suggest changes or corrections. The plan is to convert the Wiki in the coming weeks into a standalone document that we can reference in the MPI 2.2 standard. In particular, we still need to document existing, platform specific extensions to MPIR. If you are aware of such an extension, please add it to the Wiki page.
Thanks,
Martin
_______________________________________________________________________ Martin Schulz, [email protected], http://people.llnl.gov/schulz6 CASC @ Lawrence Livermore National Laboratory, Livermore, USA _______________________________________________ Mpi3-tools mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-tools