- Mpi-22 - mailman3.cels.anl.gov

Re: [Mpi-22] reConfigurable MPI
by unknown＠example.com 01 Jul '10

01 Jul '10

Most discussion I have heard relates to how a running job that makes a decision, at a well defined point, to grow itself can do that. The MPI standard currently tries to cover the aspects of this which fit within a library model and leave the resource manager outside the standard. This does not seem to be your focus. Tell me if I have misunderstood. You seem to be interested in the situation where resources are added to a cluster (or maybe freed up by other jobs completing) and having a running MPI job get notified asynchronously that there are newly available resources it can make a bid for. This idea of the cluster manager pushing resources to a job without regard to where the job is in its execution would bring lots of new issues. I am not aware of anybody having made a serious attempt to even define what would be needed inside the MPI standard to let applications catch and act on an asynchronous notification like this. My first guess is that pushing an offer of additional resource would not be very hard to design into a resource manager but the MPI API side of how to react asynchronously to that offer would be very complex. Either way (Running job decides to try for more resource vs resource manager tries to volunteer more resource to running job) I think the MPI standard can not try to specify very much about how the resource manager does its part. Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 <snip> > As you said, That paragraph is in the context of process creating > and yes! my question was about runtime reconfiguration of an MPI > cluster (whole) based on dynamic application requirements. But I > think that would be impossible without having a flexible resource > control. When a new node joins a cluster some pre-works must be done > to enable that new node act as a member of that cluster (in run > time), also, some one must be informed about new resources which > just have been added to the cluster by entrance of new node and I > think all these preparations need that missing flexible resource manager. > > > > Regards, > Siavash_______________________________________________ > mpi-22 mailing list > mpi-22_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 *

1 0

Re: [Mpi-22] reConfigurable MPI
by unknown＠example.com 30 Jun '10

30 Jun '10

> > 1) The 2.2 standard was an update to the 2.0 standard which predates > the 2006 paper you referenced. 2.2 only introduced new functions where > there was an urgent need. New features are intended for the forthcoming > 3.0. > The forum was unable to reach a consensus, and rather than make a poor > specification, they left it undefined. Now I completely got the "Why?" answer. Thanks. > 2) The resource control paragraph is in the context of process > creation and my quick 1 minute scan of the paper you referenced indicates > that it is discussing reconfiguring communication and does not talk about > dynamic processes. > Note that the info argument to the spawn routines, for example, provides a > way to communicate with a resource manager; it was an explicit goal of the > design of info to provide this way to communication information that is > outside of the specification As you said, That paragraph is in the context of process creating and yes! my question was about runtime reconfiguration of an MPI cluster (whole) based on dynamic application requirements. But I think that would be impossible without having a flexible resource control. When a new node joins a cluster some pre-works must be done to enable that new node act as a member of that cluster (in run time), also, some one must be informed about new resources which just have been added to the cluster by entrance of new node and I think all these preparations need that missing flexible resource manager. Regards, Siavash *

1 0

Re: [Mpi-22] reConfigurable MPI
by unknown＠example.com 30 Jun '10

30 Jun '10

I think the statement explains it - during the MPI 2 discussions, there was a lot of effort spent on defining a portable, standard, resource control specification. The forum was unable to reach a consensus, and rather than make a poor specification, they left it undefined. This permits MPI implementations to explore interfaces with their resource management systems (and permits an MPI-based cluster to be reconfigurable), just not in a MPI-standard defined way. Note that the info argument to the spawn routines, for example, provides a way to communicate with a resource manager; it was an explicit goal of the design of info to provide this way to communication information that is outside of the specification. Bill On Jun 30, 2010, at 2:56 PM, siavash ghiasvand wrote: > Hi, > > In MPI22 Standard document [1] on page 305 lines 27-30 we can see > this paragraph: > > The MPI Forum decided not to address resource control because it was > not able to > design a portable interface that would be appropriate for the broad > spectrum of existing > and potential resource and process controllers. Resource control can > encompass a wide > range of abilities, including adding and deleting nodes from a > virtual parallel machine, ... > > Which means, an MPI-based cluster is not reconfigurable at run time! > but in EuroPVM/MPI 2006 a reconfigurable version of MPI for HPC > clusters was described by University of New Mexico Scalable Systems > Lab [2] and they show that their implementation will enhance > performance (the main goal of MPI). So, why in MPI22 standard "The > MPI forum decided not to address resource control" which can improve > both flexibility and performance of an MPI-based cluster? > > > Ref: > MPI/CTP: A Reconfigurable MPI for HPC Applications > > > Regards, > Siavash > <ATT00001..txt> William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign *

1 0

Re: [Mpi-22] reConfigurable MPI
by unknown＠example.com 30 Jun '10

30 Jun '10

Hi Siavash, A couple of reasons for this statement: 1) The 2.2 standard was an update to the 2.0 standard which predates the 2006 paper you referenced. 2.2 only introduced new functions where there was an urgent need. New features are intended for the forthcoming 3.0. 2) The resource control paragraph is in the context of process creation and my quick 1 minute scan of the paper you referenced indicates that it is discussing reconfiguring communication and does not talk about dynamic processes. Thanks, Dave Solt From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of siavash ghiasvand Sent: Wednesday, June 30, 2010 2:57 PM To: mpi-22_at_[hidden] Subject: [Mpi-22] reConfigurable MPI Hi, In MPI22 Standard document [1<http://www.mpi-forum.org/docs/mpi-2.2/mpi22-report.pdf>] on page 305 lines 27-30 we can see this paragraph: The MPI Forum decided not to address resource control because it was not able to design a portable interface that would be appropriate for the broad spectrum of existing and potential resource and process controllers. Resource control can encompass a wide range of abilities, including adding and deleting nodes from a virtual parallel machine, ... Which means, an MPI-based cluster is not reconfigurable at run time! but in EuroPVM/MPI 2006 a reconfigurable version of MPI for HPC clusters was described by University of New Mexico Scalable Systems Lab [2<http://www.pvmmpi06.org/talks/CommProt/venkata.pdf>] and they show that their implementation will enhance performance (the main goal of MPI). So, why in MPI22 standard "The MPI forum decided not to address resource control" which can improve both flexibility and performance of an MPI-based cluster? Ref: MPI/CTP: A Reconfigurable MPI for HPC Applications<http://www.springerlink.com/content/w588601267363238/> Regards, Siavash *

1 0

reConfigurable MPI
by unknown＠example.com 30 Jun '10

30 Jun '10

Hi, In MPI22 Standard document [*1*<http://www.mpi-forum.org/docs/mpi-2.2/mpi22-report.pdf>] on page 305 lines 27-30 we can see this paragraph: > The MPI Forum decided not to address resource control because it was not > able to > design a portable interface that would be appropriate for the broad spectrum > of existing > and potential resource and process controllers. Resource control can > encompass a wide > range of abilities, including adding and deleting nodes from a virtual > parallel machine, ... > Which means, an MPI-based cluster is not reconfigurable at run time! but in EuroPVM/MPI 2006 a reconfigurable version of MPI for HPC clusters was described by University of New Mexico Scalable Systems Lab [*2*<http://www.pvmmpi06.org/talks/CommProt/venkata.pdf>] and they show that their implementation will enhance performance (the main goal of MPI). So, why in MPI22 standard "*The MPI forum decided not to address resource control*" which can improve both flexibility and performance of an MPI-based cluster? Ref: MPI/CTP: A Reconfigurable MPI for HPC Applications<http://www.springerlink.com/content/w588601267363238/> Regards, Siavash *

1 0

Fwd: [all-osl-users] OSL server reboots
by unknown＠example.com 10 Sep '09

10 Sep '09

Except for www.mpi-forum.org, all MPI Forum web, SVN, and Trac services will be disrupted at the time indicated below. I'm guessing the outage will only last a few minutes. Begin forwarded message: > From: "Kim, DongInn" <> > Date: September 10, 2009 2:14:48 PM EDT > Subject: [all-osl-users] OSL server reboots > > Hi, > > We need to have the newer kernels installed on the OSL server > machines for the security concerns but they need to be rebooted to > put them into effect. > > The systems which need to be rebooted are: > > gibson > milliways > rontok > sourcehaven > wowbagger > frogstar > magrathea > > The downtime of systems would be at 8:00AM to 9:00AM on Friday, > September 11, 2009 due to the rebooting. > - 5:00am-6:00am Pacific US time > - 6:00am-7:00am Mountain US time > - 7:00am-8:00am Central US time > - 8:00am-9:00am Eastern US time > - 12:00pm-1:00pm GMT > > Please let me know if you have any problems or questions about this > outage. > > Regards, > > -- > - DongInn > > -- Jeff Squyres jsquyres_at_[hidden]

1 0

Re: [Mpi-22] Fwd: [MPI Forum] #171: change MPI_C_BOOL external32size to 1 byte
by unknown＠example.com 09 Sep '09

09 Sep '09

Also, for 3.0 I am going to want to have tickets for each of the changes we make, so we can track them, and be sure not to inadvertently miss changes. Rich On 9/8/09 2:27 PM, "William Gropp" <wgropp_at_[hidden]> wrote: We've used a fairly open model, as long as it is clear what the change is. Typically, this is The section, page number(s) and line(s) in the MPI 2.2 standard that are affected The text being changed The replacement text. See the MPI 2.0 errata for another example. On MPI 3.0, it is too early to begin this process. We don't even know what chapters are in MPI 3.0; it is not clear that MPI 3.0 should be written as an epsilon delta from 2.2; I'd like to see MPI 3.0 written as coherent chapters, as we did in MPI 2.0. Bill On Sep 8, 2009, at 12:06 PM, Jeff Squyres wrote: > A few followups... > > 1. How is it delineated on the ticket exactly what the errata text is > to be? I see that you indicated what it precisely is for *this* > ticket, but is there a standard form for indicating *exactly* what the > errata text is for other tickets? > > 2. Does a separate ticket need to be filed for MPI 3.0, or is it > assumed that the errata change will *also* be applied to the MPI-3.0 > latex? (you may have answered this implicitly via "We *never* change > the document LaTex with an errata vote", but I wanted to be absolutely > 100% crystal clear on this point) > > Thanks! > > > > On Sep 7, 2009, at 10:57 AM, William Gropp wrote: > >> We *never* change the document LaTex with an errata vote. Errata >> items are collected into a separate document, which is updated as >> items are approved. The standard consists of the document plus >> approved errata items. This is the same process that was used with >> MPI 2.0. Errata items normally should reference the page/line number >> in the relevant document (in this case, the 2.2 document); in this >> particular case, the errata was created before the final line and >> page >> numbers were available, and the Forum agreed that it was better to >> fix >> this through the errata process rather than delay the MPI 2.2 >> document. In this particular case, the precise errata item is >> >> In MPI 2.2, on page 433, line 22, change >> >> MPI_C_BOOL 4 >> >> to >> >> MPI_C_BOOL 1 >> >> I've updated the description to reflect this, as we discussed before >> the vote. >> >> Once an item has been voted on twice, I will prepare a PDF containing >> these items and add that to the MPI Forum web site as official errata >> (again, this is what we did for MPI 2.0). >> >> The process of creating a new version of the document is not part of >> the errata process. Should another version be desired, the errata >> should be folded into it. That is what we did with MPI 2.1. >> >> Bill >> >> On Sep 7, 2009, at 9:18 AM, Jeff Squyres wrote: >> >>> --_004_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: multipart/alternative; >>> boundary="_000_9061A41D8113495ABA045FF45071419Eciscocom_" >>> >>> --_000_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: text/plain; charset="us-ascii" >>> Content-Transfer-Encoding: quoted-printable >>> >>> Forwarding this on to the general MPI-2.2 list because I'd like to >>> ask for = >>> clarifcation on the MPI-2.2 errata process (i.e., what *exactly* did >>> we vot= >>> e for on ticket #171?)... >>> >>> >>> Begin forwarded message: >>> >>> From: "MPI Forum" <mpi-22_at_[hidden]<mailto:mpi-22_at_lists.mpi-forum= >>> .org>> >>> Date: September 7, 2009 10:13:23 AM EDT >>> Subject: Re: [MPI Forum] #171: change MPI_C_BOOL external32 size to >>> 1 byte >>> >>> >>> #171: change MPI_C_BOOL external32 size to 1 byte >>> ------------------------------------------------------- >>> +-------------------= >>> - >>> Reporter: goodell >>> | = >>> Owner: >>> Type: Correction to standard >>> | = >>> Status: new >>> Priority: Had 1st vote >>> | = >>> Milestone: 2009/09/02 Helsinki >>> Version: MPI 2.2 errata >>> | = >>> Keywords: >>> Implementation: Unnecessary | >>> Author_b= >>> ill_gropp: 0 >>> Author_rich_graham: 0 | >>> Author_a= >>> dam_moody: 0 >>> Author_torsten_hoefler: 0 | >>> Author_dick= >>> _treumann: 0 >>> Author_jesper_larsson_traeff: 0 | >>> Author_georg= >>> e_bosilca: 0 >>> Author_david_solt: 0 | >>> Author_bronis_de= >>> _supinski: 0 >>> Author_rajeev_thakur: 1 | >>> Author_jef= >>> f_squyres: 0 >>> Author_alexander_supalov: 0 | >>> Author_rolf_rab= >>> enseifner: 0 >>> ------------------------------------------------------- >>> +-------------------= >>> - >>> >>> Comment(by jsquyres): >>> >>> After a little reflection, I'm a bit unclear on '''exactly''' what >> we >>> voted on for this ticket. >>> >>> Specifically, is this ticket a request to change the MPI-2.2 latex? >>> If >>> so, it is not in the proper form -- it should have the proper >>> sections for >>> all tickets. >>> >>> Or is this a ticket to add a bullet to the not-yet-created MPI-2.2 >>> errata >>> document? If so, I don't see clearly delineated what text >>> '''exactly''' >>> is going into the new errata document. >>> >>> To be more clear: I believe that the entire MPI-2.2 errata process >>> needs >>> to be laid out. It seems clear to me that we need ''both'' changes >>> to the >>> MPI-2.2 latex (for the 2.3 or 3.0 or whatever the next MPI version >>> document is) ''and'' a bullet for the MPI-2.2 errata document. Are >>> there >>> supposed to be two tickets; one for each item? Or should errata >>> tickets >>> have text for both documents (line-by-line changes compared to >> MPI-2.2 >>> ''and'' a bullet item for the MPI-2.2 errata document)? >>> >>> I understand the urgency of this ticket, but I repeat something that >>> Bill >>> said many times in Helsinki: above all else, the process must be >>> preserved >>> (in this case: defined!). Pending clarification to the the MPI-2.2 >>> errata >>> process, we might need to reset the clock on this ticket. >>> >>> -- >>> Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/ >>> 171#commen= >>> t:7> >>> MPI Forum <https://svn.mpi-forum.org/> >>> MPI Forum >>> >>> >>> -- >>> Jeff Squyres >>> jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]> >>> >>> >>> --_000_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: text/html; charset="us-ascii" >>> Content-Transfer-Encoding: quoted-printable >>> >>> <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: >>> space; -webk= >>> it-line-break: after-white-space; ">Forwarding this on to the >>> general MPI-2= >>> .2 list because I'd like to ask for clarifcation on the MPI-2.2 >>> errata proc= >>> ess (i.e., what *exactly* did we vote for on ticket >>> #171?)...<div><br><div>= >>> <br><div>Begin forwarded message:</div><br class=3D"Apple- >>> interchange-newli= >>> ne"><blockquote type=3D"cite"><div><div style=3D"margin-top: 0px; >>> margin-ri= >>> ght: 0px; margin-bottom: 0px; margin-left: 0px; "><font >>> face=3D"Helvetica" = >>> size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: >>> #00000= >>> 0"><b>From: </b></font><font face=3D"Helvetica" size=3D"5" >>> style=3D"font: 1= >>> 8.0px Helvetica">"MPI Forum" <<a href=3D"mailto:mpi-22_at_lists.mpi-forum.o= >>> rg">mpi-22_at_[hidden]</a>></font></div><div >>> style=3D"margin-top= >>> : 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; >>> "><font fac= >>> e=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: 18.0px >>> Helvetic= >>> a; color: #000000"><b>Date: </b></font><font face=3D"Helvetica" >>> size=3D"5" = >>> style=3D"font: 18.0px Helvetica">September 7, 2009 10:13:23 AM EDT</ >>> font></= >>> div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: >>> 0px; m= >>> argin-left: 0px; "><font face=3D"Helvetica" size=3D"5" >>> color=3D"#000000" st= >>> yle=3D"font: 18.0px Helvetica; color: #000000"><b>Subject: </b></ >>> font><font= >>> face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px >>> Helvetica"><b>Re: [MPI= >>> Forum] #171: change MPI_C_BOOL external32 size to 1 byte</b></ >> font></ >>> div><= >>> div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; >>> margin= >>> -left: 0px; min-height: 14px; "><br></div> </div> <div> <p><font size=3D"2">#171: change MPI_C_BOOL >>> external3= >>> 2 size to 1 byte<br> >>> ------------------------------------------------------= >>> -+--------------------<br> >>> = >>> >>> Reporter= >>> : >>> goodell = >>> | >>> &= >>> nbsp >>> ;&nbsp >>> ; &nbs= >>> p; >>> Owner: = >>> &nbsp >>> ;&nbsp >>> ; <br= >>>> &nbsp >>> >>> >> ; &= >>> nbsp; >>> Type:&nbs= >>> p; Correction to standard | >>> = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; Status: >>> new = >>> <br> >>> &nbs= >>> p >>> ;&nbsp >>> >> ; &= >>> nbsp; Priority: Had 1st >>> vote &nbsp= >>> ; | >>> = >>> >>> Mileston= >>> e: 2009/09/02 Helsinki<br> >>> = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; Version: MPI 2.2 >>> errata = >>> | >>> &= >>> nbsp; >>> Keywords: = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; <br> >>> &= >>> nbsp; Implementation: >>> Unnecessary= >>> &nbsp >>> >> ; | >>> &= >>> nbsp; >>> Author_bill_gro= >>> pp: >>> 0 &nbs= >>> p; <br> >>> &n= >>> bsp; Author_rich_graham: >>> 0 &= >>> nbsp >>> ;&nbsp >>> ; &nbs= >>> p; | >>> &nbsp= >>> ; Author_adam_moody: >>> 0 &nbsp= >>> ;&nbsp >>> >> ;&nbsp >> ; <b= >>> r> &nb >> >> William Gropp >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Paul and Cynthia Saylor Professor of Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> _______________________________________________ >> mpi-22 mailing list >> mpi-22_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 >> > > > -- > Jeff Squyres > jsquyres_at_[hidden] > > _______________________________________________ > mpi-22 mailing list > mpi-22_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign _______________________________________________ mpi-22 mailing list mpi-22_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22

1 0

Re: [Mpi-22] Fwd: [MPI Forum] #171: change MPI_C_BOOL external32size to 1 byte
by unknown＠example.com 08 Sep '09

08 Sep '09

We've used a fairly open model, as long as it is clear what the change is. Typically, this is The section, page number(s) and line(s) in the MPI 2.2 standard that are affected The text being changed The replacement text. See the MPI 2.0 errata for another example. On MPI 3.0, it is too early to begin this process. We don't even know what chapters are in MPI 3.0; it is not clear that MPI 3.0 should be written as an epsilon delta from 2.2; I'd like to see MPI 3.0 written as coherent chapters, as we did in MPI 2.0. Bill On Sep 8, 2009, at 12:06 PM, Jeff Squyres wrote: > A few followups... > > 1. How is it delineated on the ticket exactly what the errata text is > to be? I see that you indicated what it precisely is for *this* > ticket, but is there a standard form for indicating *exactly* what the > errata text is for other tickets? > > 2. Does a separate ticket need to be filed for MPI 3.0, or is it > assumed that the errata change will *also* be applied to the MPI-3.0 > latex? (you may have answered this implicitly via "We *never* change > the document LaTex with an errata vote", but I wanted to be absolutely > 100% crystal clear on this point) > > Thanks! > > > > On Sep 7, 2009, at 10:57 AM, William Gropp wrote: > >> We *never* change the document LaTex with an errata vote. Errata >> items are collected into a separate document, which is updated as >> items are approved. The standard consists of the document plus >> approved errata items. This is the same process that was used with >> MPI 2.0. Errata items normally should reference the page/line number >> in the relevant document (in this case, the 2.2 document); in this >> particular case, the errata was created before the final line and >> page >> numbers were available, and the Forum agreed that it was better to >> fix >> this through the errata process rather than delay the MPI 2.2 >> document. In this particular case, the precise errata item is >> >> In MPI 2.2, on page 433, line 22, change >> >> MPI_C_BOOL 4 >> >> to >> >> MPI_C_BOOL 1 >> >> I've updated the description to reflect this, as we discussed before >> the vote. >> >> Once an item has been voted on twice, I will prepare a PDF containing >> these items and add that to the MPI Forum web site as official errata >> (again, this is what we did for MPI 2.0). >> >> The process of creating a new version of the document is not part of >> the errata process. Should another version be desired, the errata >> should be folded into it. That is what we did with MPI 2.1. >> >> Bill >> >> On Sep 7, 2009, at 9:18 AM, Jeff Squyres wrote: >> >>> --_004_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: multipart/alternative; >>> boundary="_000_9061A41D8113495ABA045FF45071419Eciscocom_" >>> >>> --_000_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: text/plain; charset="us-ascii" >>> Content-Transfer-Encoding: quoted-printable >>> >>> Forwarding this on to the general MPI-2.2 list because I'd like to >>> ask for = >>> clarifcation on the MPI-2.2 errata process (i.e., what *exactly* did >>> we vot= >>> e for on ticket #171?)... >>> >>> >>> Begin forwarded message: >>> >>> From: "MPI Forum" <mpi-22_at_[hidden]<mailto:mpi-22_at_lists.mpi-forum= >>> .org>> >>> Date: September 7, 2009 10:13:23 AM EDT >>> Subject: Re: [MPI Forum] #171: change MPI_C_BOOL external32 size to >>> 1 byte >>> >>> >>> #171: change MPI_C_BOOL external32 size to 1 byte >>> ------------------------------------------------------- >>> +-------------------= >>> - >>> Reporter: goodell >>> | = >>> Owner: >>> Type: Correction to standard >>> | = >>> Status: new >>> Priority: Had 1st vote >>> | = >>> Milestone: 2009/09/02 Helsinki >>> Version: MPI 2.2 errata >>> | = >>> Keywords: >>> Implementation: Unnecessary | >>> Author_b= >>> ill_gropp: 0 >>> Author_rich_graham: 0 | >>> Author_a= >>> dam_moody: 0 >>> Author_torsten_hoefler: 0 | >>> Author_dick= >>> _treumann: 0 >>> Author_jesper_larsson_traeff: 0 | >>> Author_georg= >>> e_bosilca: 0 >>> Author_david_solt: 0 | >>> Author_bronis_de= >>> _supinski: 0 >>> Author_rajeev_thakur: 1 | >>> Author_jef= >>> f_squyres: 0 >>> Author_alexander_supalov: 0 | >>> Author_rolf_rab= >>> enseifner: 0 >>> ------------------------------------------------------- >>> +-------------------= >>> - >>> >>> Comment(by jsquyres): >>> >>> After a little reflection, I'm a bit unclear on '''exactly''' what >> we >>> voted on for this ticket. >>> >>> Specifically, is this ticket a request to change the MPI-2.2 latex? >>> If >>> so, it is not in the proper form -- it should have the proper >>> sections for >>> all tickets. >>> >>> Or is this a ticket to add a bullet to the not-yet-created MPI-2.2 >>> errata >>> document? If so, I don't see clearly delineated what text >>> '''exactly''' >>> is going into the new errata document. >>> >>> To be more clear: I believe that the entire MPI-2.2 errata process >>> needs >>> to be laid out. It seems clear to me that we need ''both'' changes >>> to the >>> MPI-2.2 latex (for the 2.3 or 3.0 or whatever the next MPI version >>> document is) ''and'' a bullet for the MPI-2.2 errata document. Are >>> there >>> supposed to be two tickets; one for each item? Or should errata >>> tickets >>> have text for both documents (line-by-line changes compared to >> MPI-2.2 >>> ''and'' a bullet item for the MPI-2.2 errata document)? >>> >>> I understand the urgency of this ticket, but I repeat something that >>> Bill >>> said many times in Helsinki: above all else, the process must be >>> preserved >>> (in this case: defined!). Pending clarification to the the MPI-2.2 >>> errata >>> process, we might need to reset the clock on this ticket. >>> >>> -- >>> Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/ >>> 171#commen= >>> t:7> >>> MPI Forum <https://svn.mpi-forum.org/> >>> MPI Forum >>> >>> >>> -- >>> Jeff Squyres >>> jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]> >>> >>> >>> --_000_9061A41D8113495ABA045FF45071419Eciscocom_ >>> Content-Type: text/html; charset="us-ascii" >>> Content-Transfer-Encoding: quoted-printable >>> >>> <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: >>> space; -webk= >>> it-line-break: after-white-space; ">Forwarding this on to the >>> general MPI-2= >>> .2 list because I'd like to ask for clarifcation on the MPI-2.2 >>> errata proc= >>> ess (i.e., what *exactly* did we vote for on ticket >>> #171?)...<div><br><div>= >>> <br><div>Begin forwarded message:</div><br class=3D"Apple- >>> interchange-newli= >>> ne"><blockquote type=3D"cite"><div><div style=3D"margin-top: 0px; >>> margin-ri= >>> ght: 0px; margin-bottom: 0px; margin-left: 0px; "><font >>> face=3D"Helvetica" = >>> size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: >>> #00000= >>> 0"><b>From: </b></font><font face=3D"Helvetica" size=3D"5" >>> style=3D"font: 1= >>> 8.0px Helvetica">"MPI Forum" <<a href=3D"mailto:mpi-22_at_lists.mpi-forum.o= >>> rg">mpi-22_at_[hidden]</a>></font></div><div >>> style=3D"margin-top= >>> : 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; >>> "><font fac= >>> e=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: 18.0px >>> Helvetic= >>> a; color: #000000"><b>Date: </b></font><font face=3D"Helvetica" >>> size=3D"5" = >>> style=3D"font: 18.0px Helvetica">September 7, 2009 10:13:23 AM EDT</ >>> font></= >>> div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: >>> 0px; m= >>> argin-left: 0px; "><font face=3D"Helvetica" size=3D"5" >>> color=3D"#000000" st= >>> yle=3D"font: 18.0px Helvetica; color: #000000"><b>Subject: </b></ >>> font><font= >>> face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px >>> Helvetica"><b>Re: [MPI= >>> Forum] #171: change MPI_C_BOOL external32 size to 1 byte</b></ >> font></ >>> div><= >>> div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; >>> margin= >>> -left: 0px; min-height: 14px; "><br></div> </div> <div> <p><font size=3D"2">#171: change MPI_C_BOOL >>> external3= >>> 2 size to 1 byte<br> >>> ------------------------------------------------------= >>> -+--------------------<br> >>> = >>> >>> Reporter= >>> : >>> goodell = >>> | >>> &= >>> nbsp >>> ;&nbsp >>> ; &nbs= >>> p; >>> Owner: = >>> &nbsp >>> ;&nbsp >>> ; <br= >>>> &nbsp >>> >>> >> ; &= >>> nbsp; >>> Type:&nbs= >>> p; Correction to standard | >>> = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; Status: >>> new = >>> <br> >>> &nbs= >>> p >>> ;&nbsp >>> >> ; &= >>> nbsp; Priority: Had 1st >>> vote &nbsp= >>> ; | >>> = >>> >>> Mileston= >>> e: 2009/09/02 Helsinki<br> >>> = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; Version: MPI 2.2 >>> errata = >>> | >>> &= >>> nbsp; >>> Keywords: = >>> &nbsp >>> ;&nbsp >>> ; &nb= >>> sp; <br> >>> &= >>> nbsp; Implementation: >>> Unnecessary= >>> &nbsp >>> >> ; | >>> &= >>> nbsp; >>> Author_bill_gro= >>> pp: >>> 0 &nbs= >>> p; <br> >>> &n= >>> bsp; Author_rich_graham: >>> 0 &= >>> nbsp >>> ;&nbsp >>> ; &nbs= >>> p; | >>> &nbsp= >>> ; Author_adam_moody: >>> 0 &nbsp= >>> ;&nbsp >>> >> ;&nbsp >> ; <b= >>> r> &nb >> >> William Gropp >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Paul and Cynthia Saylor Professor of Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> _______________________________________________ >> mpi-22 mailing list >> mpi-22_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 >> > > > -- > Jeff Squyres > jsquyres_at_[hidden] > > _______________________________________________ > mpi-22 mailing list > mpi-22_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

1 0

Re: [Mpi-22] Fwd: [MPI Forum] #171: change MPI_C_BOOL external32size to 1 byte
by unknown＠example.com 08 Sep '09

08 Sep '09

A few followups... 1. How is it delineated on the ticket exactly what the errata text is to be? I see that you indicated what it precisely is for *this* ticket, but is there a standard form for indicating *exactly* what the errata text is for other tickets? 2. Does a separate ticket need to be filed for MPI 3.0, or is it assumed that the errata change will *also* be applied to the MPI-3.0 latex? (you may have answered this implicitly via "We *never* change the document LaTex with an errata vote", but I wanted to be absolutely 100% crystal clear on this point) Thanks! On Sep 7, 2009, at 10:57 AM, William Gropp wrote: > We *never* change the document LaTex with an errata vote. Errata > items are collected into a separate document, which is updated as > items are approved. The standard consists of the document plus > approved errata items. This is the same process that was used with > MPI 2.0. Errata items normally should reference the page/line number > in the relevant document (in this case, the 2.2 document); in this > particular case, the errata was created before the final line and page > numbers were available, and the Forum agreed that it was better to fix > this through the errata process rather than delay the MPI 2.2 > document. In this particular case, the precise errata item is > > In MPI 2.2, on page 433, line 22, change > > MPI_C_BOOL 4 > > to > > MPI_C_BOOL 1 > > I've updated the description to reflect this, as we discussed before > the vote. > > Once an item has been voted on twice, I will prepare a PDF containing > these items and add that to the MPI Forum web site as official errata > (again, this is what we did for MPI 2.0). > > The process of creating a new version of the document is not part of > the errata process. Should another version be desired, the errata > should be folded into it. That is what we did with MPI 2.1. > > Bill > > On Sep 7, 2009, at 9:18 AM, Jeff Squyres wrote: > > > --_004_9061A41D8113495ABA045FF45071419Eciscocom_ > > Content-Type: multipart/alternative; > > boundary="_000_9061A41D8113495ABA045FF45071419Eciscocom_" > > > > --_000_9061A41D8113495ABA045FF45071419Eciscocom_ > > Content-Type: text/plain; charset="us-ascii" > > Content-Transfer-Encoding: quoted-printable > > > > Forwarding this on to the general MPI-2.2 list because I'd like to > > ask for = > > clarifcation on the MPI-2.2 errata process (i.e., what *exactly* did > > we vot= > > e for on ticket #171?)... > > > > > > Begin forwarded message: > > > > From: "MPI Forum" <mpi-22_at_[hidden]<mailto:mpi-22_at_lists.mpi-forum= > > .org>> > > Date: September 7, 2009 10:13:23 AM EDT > > Subject: Re: [MPI Forum] #171: change MPI_C_BOOL external32 size to > > 1 byte > > > > > > #171: change MPI_C_BOOL external32 size to 1 byte > > ------------------------------------------------------- > > +-------------------= > > - > > Reporter: goodell > > | = > > Owner: > > Type: Correction to standard > > | = > > Status: new > > Priority: Had 1st vote > > | = > > Milestone: 2009/09/02 Helsinki > > Version: MPI 2.2 errata > > | = > > Keywords: > > Implementation: Unnecessary | > > Author_b= > > ill_gropp: 0 > > Author_rich_graham: 0 | > > Author_a= > > dam_moody: 0 > > Author_torsten_hoefler: 0 | > > Author_dick= > > _treumann: 0 > > Author_jesper_larsson_traeff: 0 | > > Author_georg= > > e_bosilca: 0 > > Author_david_solt: 0 | > > Author_bronis_de= > > _supinski: 0 > > Author_rajeev_thakur: 1 | > > Author_jef= > > f_squyres: 0 > > Author_alexander_supalov: 0 | > > Author_rolf_rab= > > enseifner: 0 > > ------------------------------------------------------- > > +-------------------= > > - > > > > Comment(by jsquyres): > > > > After a little reflection, I'm a bit unclear on '''exactly''' what > we > > voted on for this ticket. > > > > Specifically, is this ticket a request to change the MPI-2.2 latex? > > If > > so, it is not in the proper form -- it should have the proper > > sections for > > all tickets. > > > > Or is this a ticket to add a bullet to the not-yet-created MPI-2.2 > > errata > > document? If so, I don't see clearly delineated what text > > '''exactly''' > > is going into the new errata document. > > > > To be more clear: I believe that the entire MPI-2.2 errata process > > needs > > to be laid out. It seems clear to me that we need ''both'' changes > > to the > > MPI-2.2 latex (for the 2.3 or 3.0 or whatever the next MPI version > > document is) ''and'' a bullet for the MPI-2.2 errata document. Are > > there > > supposed to be two tickets; one for each item? Or should errata > > tickets > > have text for both documents (line-by-line changes compared to > MPI-2.2 > > ''and'' a bullet item for the MPI-2.2 errata document)? > > > > I understand the urgency of this ticket, but I repeat something that > > Bill > > said many times in Helsinki: above all else, the process must be > > preserved > > (in this case: defined!). Pending clarification to the the MPI-2.2 > > errata > > process, we might need to reset the clock on this ticket. > > > > -- > > Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/ > > 171#commen= > > t:7> > > MPI Forum <https://svn.mpi-forum.org/> > > MPI Forum > > > > > > -- > > Jeff Squyres > > jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]> > > > > > > --_000_9061A41D8113495ABA045FF45071419Eciscocom_ > > Content-Type: text/html; charset="us-ascii" > > Content-Transfer-Encoding: quoted-printable > > > > <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: > > space; -webk= > > it-line-break: after-white-space; ">Forwarding this on to the > > general MPI-2= > > .2 list because I'd like to ask for clarifcation on the MPI-2.2 > > errata proc= > > ess (i.e., what *exactly* did we vote for on ticket > > #171?)...<div><br><div>= > > <br><div>Begin forwarded message:</div><br class=3D"Apple- > > interchange-newli= > > ne"><blockquote type=3D"cite"><div><div style=3D"margin-top: 0px; > > margin-ri= > > ght: 0px; margin-bottom: 0px; margin-left: 0px; "><font > > face=3D"Helvetica" = > > size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: > > #00000= > > 0"><b>From: </b></font><font face=3D"Helvetica" size=3D"5" > > style=3D"font: 1= > > 8.0px Helvetica">"MPI Forum" <<a href=3D"mailto:mpi-22_at_lists.mpi-forum.o= > > rg">mpi-22_at_[hidden]</a>></font></div><div > > style=3D"margin-top= > > : 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; > > "><font fac= > > e=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: 18.0px > > Helvetic= > > a; color: #000000"><b>Date: </b></font><font face=3D"Helvetica" > > size=3D"5" = > > style=3D"font: 18.0px Helvetica">September 7, 2009 10:13:23 AM EDT</ > > font></= > > div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: > > 0px; m= > > argin-left: 0px; "><font face=3D"Helvetica" size=3D"5" > > color=3D"#000000" st= > > yle=3D"font: 18.0px Helvetica; color: #000000"><b>Subject: </b></ > > font><font= > > face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px > > Helvetica"><b>Re: [MPI= > > Forum] #171: change MPI_C_BOOL external32 size to 1 byte</b></ > font></ > > div><= > > div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; > > margin= > > -left: 0px; min-height: 14px; "><br></div> </div> <div> <p><font size=3D"2">#171: change MPI_C_BOOL > > external3= > > 2 size to 1 byte<br> > > ------------------------------------------------------= > > -+--------------------<br> > > = > > > > Reporter= > > : > > goodell = > > | > > &= > > nbsp > > ;&nbsp > > ; &nbs= > > p; > > Owner: = > > &nbsp > > ;&nbsp > > ; <br= > >> &nbsp > > > > > ; &= > > nbsp; > > Type:&nbs= > > p; Correction to standard | > > = > > &nbsp > > ;&nbsp > > ; &nb= > > sp; Status: > > new = > > <br> > > &nbs= > > p > > ;&nbsp > > > ; &= > > nbsp; Priority: Had 1st > > vote &nbsp= > > ; | > > = > > > > Mileston= > > e: 2009/09/02 Helsinki<br> > > = > > &nbsp > > ;&nbsp > > ; &nb= > > sp; Version: MPI 2.2 > > errata = > > | > > &= > > nbsp; > > Keywords: = > > &nbsp > > ;&nbsp > > ; &nb= > > sp; <br> > > &= > > nbsp; Implementation: > > Unnecessary= > > &nbsp > > > ; | > > &= > > nbsp; > > Author_bill_gro= > > pp: > > 0 &nbs= > > p; <br> > > &n= > > bsp; Author_rich_graham: > > 0 &= > > nbsp > > ;&nbsp > > ; &nbs= > > p; | > > &nbsp= > > ; Author_adam_moody: > > 0 &nbsp= > > ;&nbsp > > > ;&nbsp > ; <b= > > r> &nb > > William Gropp > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > > > > _______________________________________________ > mpi-22 mailing list > mpi-22_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22 > -- Jeff Squyres jsquyres_at_[hidden]

1 0

Re: [Mpi-22] Fwd: [MPI Forum] #171: change MPI_C_BOOL external32 size to 1 byte
by unknown＠example.com 07 Sep '09

07 Sep '09

We *never* change the document LaTex with an errata vote. Errata items are collected into a separate document, which is updated as items are approved. The standard consists of the document plus approved errata items. This is the same process that was used with MPI 2.0. Errata items normally should reference the page/line number in the relevant document (in this case, the 2.2 document); in this particular case, the errata was created before the final line and page numbers were available, and the Forum agreed that it was better to fix this through the errata process rather than delay the MPI 2.2 document. In this particular case, the precise errata item is In MPI 2.2, on page 433, line 22, change MPI_C_BOOL 4 to MPI_C_BOOL 1 I've updated the description to reflect this, as we discussed before the vote. Once an item has been voted on twice, I will prepare a PDF containing these items and add that to the MPI Forum web site as official errata (again, this is what we did for MPI 2.0). The process of creating a new version of the document is not part of the errata process. Should another version be desired, the errata should be folded into it. That is what we did with MPI 2.1. Bill On Sep 7, 2009, at 9:18 AM, Jeff Squyres wrote: > --_004_9061A41D8113495ABA045FF45071419Eciscocom_ > Content-Type: multipart/alternative; > boundary="_000_9061A41D8113495ABA045FF45071419Eciscocom_" > > --_000_9061A41D8113495ABA045FF45071419Eciscocom_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Forwarding this on to the general MPI-2.2 list because I'd like to > ask for = > clarifcation on the MPI-2.2 errata process (i.e., what *exactly* did > we vot= > e for on ticket #171?)... > > > Begin forwarded message: > > From: "MPI Forum" <mpi-22_at_[hidden]<mailto:mpi-22_at_lists.mpi-forum= > .org>> > Date: September 7, 2009 10:13:23 AM EDT > Subject: Re: [MPI Forum] #171: change MPI_C_BOOL external32 size to > 1 byte > > > #171: change MPI_C_BOOL external32 size to 1 byte > ------------------------------------------------------- > +-------------------= > - > Reporter: goodell > | = > Owner: > Type: Correction to standard > | = > Status: new > Priority: Had 1st vote > | = > Milestone: 2009/09/02 Helsinki > Version: MPI 2.2 errata > | = > Keywords: > Implementation: Unnecessary | > Author_b= > ill_gropp: 0 > Author_rich_graham: 0 | > Author_a= > dam_moody: 0 > Author_torsten_hoefler: 0 | > Author_dick= > _treumann: 0 > Author_jesper_larsson_traeff: 0 | > Author_georg= > e_bosilca: 0 > Author_david_solt: 0 | > Author_bronis_de= > _supinski: 0 > Author_rajeev_thakur: 1 | > Author_jef= > f_squyres: 0 > Author_alexander_supalov: 0 | > Author_rolf_rab= > enseifner: 0 > ------------------------------------------------------- > +-------------------= > - > > Comment(by jsquyres): > > After a little reflection, I'm a bit unclear on '''exactly''' what we > voted on for this ticket. > > Specifically, is this ticket a request to change the MPI-2.2 latex? > If > so, it is not in the proper form -- it should have the proper > sections for > all tickets. > > Or is this a ticket to add a bullet to the not-yet-created MPI-2.2 > errata > document? If so, I don't see clearly delineated what text > '''exactly''' > is going into the new errata document. > > To be more clear: I believe that the entire MPI-2.2 errata process > needs > to be laid out. It seems clear to me that we need ''both'' changes > to the > MPI-2.2 latex (for the 2.3 or 3.0 or whatever the next MPI version > document is) ''and'' a bullet for the MPI-2.2 errata document. Are > there > supposed to be two tickets; one for each item? Or should errata > tickets > have text for both documents (line-by-line changes compared to MPI-2.2 > ''and'' a bullet item for the MPI-2.2 errata document)? > > I understand the urgency of this ticket, but I repeat something that > Bill > said many times in Helsinki: above all else, the process must be > preserved > (in this case: defined!). Pending clarification to the the MPI-2.2 > errata > process, we might need to reset the clock on this ticket. > > -- > Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/ > 171#commen= > t:7> > MPI Forum <https://svn.mpi-forum.org/> > MPI Forum > > > -- > Jeff Squyres > jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]> > > > --_000_9061A41D8113495ABA045FF45071419Eciscocom_ > Content-Type: text/html; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: > space; -webk= > it-line-break: after-white-space; ">Forwarding this on to the > general MPI-2= > .2 list because I'd like to ask for clarifcation on the MPI-2.2 > errata proc= > ess (i.e., what *exactly* did we vote for on ticket > #171?)...<div><br><div>= > <br><div>Begin forwarded message:</div><br class=3D"Apple- > interchange-newli= > ne"><blockquote type=3D"cite"><div><div style=3D"margin-top: 0px; > margin-ri= > ght: 0px; margin-bottom: 0px; margin-left: 0px; "><font > face=3D"Helvetica" = > size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: > #00000= > 0"><b>From: </b></font><font face=3D"Helvetica" size=3D"5" > style=3D"font: 1= > 8.0px Helvetica">"MPI Forum" <<a href=3D"mailto:mpi-22_at_lists.mpi-forum.o= > rg">mpi-22_at_[hidden]</a>></font></div><div > style=3D"margin-top= > : 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; > "><font fac= > e=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: 18.0px > Helvetic= > a; color: #000000"><b>Date: </b></font><font face=3D"Helvetica" > size=3D"5" = > style=3D"font: 18.0px Helvetica">September 7, 2009 10:13:23 AM EDT</ > font></= > div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: > 0px; m= > argin-left: 0px; "><font face=3D"Helvetica" size=3D"5" > color=3D"#000000" st= > yle=3D"font: 18.0px Helvetica; color: #000000"><b>Subject: </b></ > font><font= > face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px > Helvetica"><b>Re: [MPI= > Forum] #171: change MPI_C_BOOL external32 size to 1 byte</b></font></ > div><= > div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; > margin= > -left: 0px; min-height: 14px; "><br></div> </div> <div> <p><font size=3D"2">#171: change MPI_C_BOOL > external3= > 2 size to 1 byte<br> > ------------------------------------------------------= > -+--------------------<br> > = > > Reporter= > : > goodell = > | > &= > nbsp > ;&nbsp > ; &nbs= > p; > Owner: = > &nbsp > ;&nbsp > ; <br= >> &nbsp >> ; &= > nbsp; > Type:&nbs= > p; Correction to standard | > = > &nbsp > ;&nbsp > ; &nb= > sp; Status: > new = > <br> > &nbs= > p > ;&nbsp > ; &= > nbsp; Priority: Had 1st > vote &nbsp= > ; | > = > > Mileston= > e: 2009/09/02 Helsinki<br> > = > &nbsp > ;&nbsp > ; &nb= > sp; Version: MPI 2.2 > errata = > | > &= > nbsp; > Keywords: = > &nbsp > ;&nbsp > ; &nb= > sp; <br> > &= > nbsp; Implementation: > Unnecessary= > &nbsp > ; | > &= > nbsp; > Author_bill_gro= > pp: > 0 &nbs= > p; <br> > &n= > bsp; Author_rich_graham: > 0 &= > nbsp > ;&nbsp > ; &nbs= > p; | > &nbsp= > ; Author_adam_moody: > 0 &nbsp= > ;&nbsp > ; <b= > r> &nb William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

1 0