From david.solt at [hidden] Tue Apr 5 11:12:19 2011 From: david.solt at [hidden] (Solt, David George) Date: Tue, 5 Apr 2011 16:12:19 +0000 Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback In-Reply-To: <91B583BE4B6FCD408F53D1B8F537E0921D78742F@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> Message-ID: > Page numbers are Acrobat page numbers, not document page numbers. Page numbers are random and do not appear to be associated with any document in the known universe :) >Page9_at_19: ...count values, and that type is MPI_Count... >Page9_at_29: confusion about 'type map' applying to memory only, not file view >Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. Left for next concall > Page24_at_9: MPI_COUNT should be MPI_Count - done > Page91_at_11: "value of size to" size should be a different font. - done > Page92_at_15: Add "The Functions MPI_TYPE_GET_EXTENT" - done, changed to "The functions MPI_TYPE_GET_EXTENT and ..." > Page94_at_33: Start sentence properly, not with 'true_lb' (Ticket0 for Adam) Left for Adam since this is not text we changed > Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) > Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. Left for next concall >In MPI Forum 3.0 draft 1 document: >Page455_at_32 add MPI_COUNT as width = 8 in external32 -done Thanks, Dave -----Original Message----- From: mpi3-bwcompat-bounces_at_[hidden] [mailto:mpi3-bwcompat-bounces_at_[hidden]] On Behalf Of Fab Tillier Sent: Wednesday, March 30, 2011 10:44 AM To: MPI-3 backwards compatability WG (mpi3-bwcompat_at_[hidden]) Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback Page numbers are Acrobat page numbers, not document page numbers. Page9_at_19: ...count values, and that type is MPI_Count... Page9_at_29: confusion about 'type map' applying to memory only, not file view Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. Page24_at_9: MPI_COUNT should be MPI_Count Page91_at_11: "value of size to" size should be a different font. Page92_at_15: Add "The Functions MPI_TYPE_GET_EXTENT" Page94_at_33: Start sentence properly, not with 'true_lb' (Ticket0 for Adam) Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. In MPI Forum 3.0 draft 1 document: Page455_at_32 add MPI_COUNT as width = 8 in external32 _______________________________________________ Mpi3-bwcompat mailing list Mpi3-bwcompat_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat From jsquyres at [hidden] Mon Apr 11 16:10:55 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 11 Apr 2011 17:10:55 -0400 Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback In-Reply-To: Message-ID: <34DF4B8E-EACE-4627-8F8C-4231C0B05046@cisco.com> Note that there is not much time before the next Forum meeting. To get this in the pre-requisite 2 weeks before the Forum meeting, we have to send around a new document by *Monday, May 25*. Or *exactly 2 weeks from today*. How do we want to make immediate progress on the doc so that we can meet this deadline? On Apr 5, 2011, at 12:12 PM, Solt, David George wrote: >> Page numbers are Acrobat page numbers, not document page numbers. > > Page numbers are random and do not appear to be associated with any document in the known universe :) > >> Page9_at_19: ...count values, and that type is MPI_Count... >> Page9_at_29: confusion about 'type map' applying to memory only, not file view >> Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. > > Left for next concall > >> Page24_at_9: MPI_COUNT should be MPI_Count > - done >> Page91_at_11: "value of size to" size should be a different font. > - done >> Page92_at_15: Add "The Functions MPI_TYPE_GET_EXTENT" > - done, changed to "The functions MPI_TYPE_GET_EXTENT and ..." > >> Page94_at_33: Start sentence properly, not with 'true_lb' (Ticket0 for Adam) > > Left for Adam since this is not text we changed > >> Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) >> Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. > > Left for next concall > >> In MPI Forum 3.0 draft 1 document: >> Page455_at_32 add MPI_COUNT as width = 8 in external32 > -done > > Thanks, > Dave > > -----Original Message----- > From: mpi3-bwcompat-bounces_at_[hidden] [mailto:mpi3-bwcompat-bounces_at_[hidden]] On Behalf Of Fab Tillier > Sent: Wednesday, March 30, 2011 10:44 AM > To: MPI-3 backwards compatability WG (mpi3-bwcompat_at_[hidden]) > Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback > > Page numbers are Acrobat page numbers, not document page numbers. > > Page9_at_19: ...count values, and that type is MPI_Count... > Page9_at_29: confusion about 'type map' applying to memory only, not file view > Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. > Page24_at_9: MPI_COUNT should be MPI_Count > Page91_at_11: "value of size to" size should be a different font. > Page92_at_15: Add "The Functions MPI_TYPE_GET_EXTENT" > Page94_at_33: Start sentence properly, not with 'true_lb' (Ticket0 for Adam) > Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) > Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. > > In MPI Forum 3.0 draft 1 document: > Page455_at_32 add MPI_COUNT as width = 8 in external32 > > _______________________________________________ > Mpi3-bwcompat mailing list > Mpi3-bwcompat_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat > > _______________________________________________ > Mpi3-bwcompat mailing list > Mpi3-bwcompat_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ From jsquyres at [hidden] Mon Apr 11 16:13:16 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 11 Apr 2011 17:13:16 -0400 Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback In-Reply-To: <34DF4B8E-EACE-4627-8F8C-4231C0B05046@cisco.com> Message-ID: <00F522AF-09C2-41E7-BF0C-DA22CD2A27F1@cisco.com> On Apr 11, 2011, at 5:10 PM, Jeff Squyres wrote: > Note that there is not much time before the next Forum meeting. > > To get this in the pre-requisite 2 weeks before the Forum meeting, we have to send around a new document by *Monday, May 25*. Or *exactly 2 weeks from today*. Er... I meant *Monday, APRIL 25*. :-) -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ From david.solt at [hidden] Mon Apr 11 21:19:36 2011 From: david.solt at [hidden] (Solt, David George) Date: Tue, 12 Apr 2011 02:19:36 +0000 Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback In-Reply-To: <00F522AF-09C2-41E7-BF0C-DA22CD2A27F1@cisco.com> Message-ID: We have a call scheduled this Friday, but we can get things rolling via e-mail before then. >> Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. Hold on... looking for a 10 foot pole.... I'm not sure I like my own suggestion, but here it is: "Most MPI routines use int in C or INTEGER in Fortran as count arguments rather than MPI_Count. Routines use MPI_Count as the type for the count argument where they are deemed most likely to exceed the storage capacity of a int or INTEGER." >> Page9_at_19: ...count values, and that type is MPI_Count... This change makes no sense to me. The very next sentence says, "The datatype of such an argument is MPI_Count...". Does someone remember what this was about? >> Page9_at_29: confusion about 'type map' applying to memory only, not file view I don't remember the rationale for our rationale :). It seems to say, "Count values need to be big enough to hold any count values". Even if we changed it to "The storage used for storing MPI_Count values needs to be large enough to hold any count values" doesn't seem any more useful a statement. Maybe this should be something of the form "Advice to Implementers: The larger the storage use for MPI_Count, the larger the type maps an application can create for working with large files and message data. >> Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) >> Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. If the number of basic elements received exceeds the limits of the count parameter, then MPI_PACK_SIZE set the value of count to MPI_UNDEFINED. For the MPI_GET_COUNT, it already says this: "(We shall later see, in Section 4.1.11, that MPI_GET_COUNT may return, in certain situations, the value MPI_UNDEFINED.)". Does that cover it or should we replace it with: If the number of basic elements received exceeds the limits of the count parameter, then MPI_GET_COUNT set the value of count to MPI_UNDEFINED. I don't think we have to distinguish between "received" and "set by MPI_STATUS_SET_ELEMENTS[X], since this is intended to implement as generalized request receive which is still a form of a "receive". Thoughts? Dave -----Original Message----- From: mpi3-bwcompat-bounces_at_[hidden] [mailto:mpi3-bwcompat-bounces_at_[hidden]] On Behalf Of Jeff Squyres Sent: Monday, April 11, 2011 4:13 PM To: MPI-3 backwards compatability WG Subject: Re: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback On Apr 11, 2011, at 5:10 PM, Jeff Squyres wrote: > Note that there is not much time before the next Forum meeting. > > To get this in the pre-requisite 2 weeks before the Forum meeting, we have to send around a new document by *Monday, May 25*. Or *exactly 2 weeks from today*. Er... I meant *Monday, APRIL 25*. :-) -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ Mpi3-bwcompat mailing list Mpi3-bwcompat_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat From jsquyres at [hidden] Thu Apr 14 08:02:50 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Thu, 14 Apr 2011 09:02:50 -0400 Subject: [Mpi3-bwcompat] MPI_Count Ticket 265 feedback In-Reply-To: Message-ID: <5033A020-498C-49A2-AA63-38A38E9835F9@cisco.com> On Apr 11, 2011, at 10:19 PM, Solt, David George wrote: > We have a call scheduled this Friday, but we can get things rolling via e-mail before then. Don't forget that we need to get 4 reviews from every chapter, too. :-\ That will suck -- please add this to the list of things to discuss on Friday. We need to start hitting up lots of chapter committees for reviews...! >>> Page9_at_30: For backward compatibility, many MPI routines use int in C or INTEGER in Fortran as count arguments. > > Hold on... looking for a 10 foot pole.... I'm not sure I like my own suggestion, but here it is: "Most MPI routines use int in C or INTEGER in Fortran as count arguments rather than MPI_Count. Routines use MPI_Count as the type for the count argument where they are deemed most likely to exceed the storage capacity of a int or INTEGER." I honestly forget what this was for -- are we adding text to the rationale here? >>> Page9_at_19: ...count values, and that type is MPI_Count... > > This change makes no sense to me. The very next sentence says, "The datatype of such an argument is MPI_Count...". Does someone remember what this was about? Agreed -- seems non-sensical. >>> Page9_at_29: confusion about 'type map' applying to memory only, not file view > > I don't remember the rationale for our rationale :). It seems to say, "Count values need to be big enough to hold any count values". Yes. Specifically, it's explaining why we need it to be the largest of all types (including file offsets, which some people might question unless further clarification is provided). > Even if we changed it to "The storage used for storing MPI_Count values needs to be large enough to hold any count values" doesn't seem any more useful a statement. Maybe this should be something of the form "Advice to Implementers: The larger the storage use for MPI_Count, the larger the type maps an application can create for working with large files and message data. No, I think the point is to provide concrete cases where counts need to be used, and are currently potentially *mis*used by the existing API functions -- e.g., file type maps. >>> Page120_at_38: Use similar wording to previous "limits" wording might be better (more consistent) >>> Need to mention overflow for MPI_GET_COUNT? One could use MPI_STATUS_SET_ELEMENTS_X to overflow MPI_GET_COUNT. > > If the number of basic elements received exceeds the limits of the count parameter, then MPI_PACK_SIZE set the value of count to MPI_UNDEFINED. > > For the MPI_GET_COUNT, it already says this: > > "(We shall later see, in Section 4.1.11, that MPI_GET_COUNT > may return, in certain situations, the value MPI_UNDEFINED.)". Does that cover it or should we replace it with: I don't think it covers it, because 4.1.11 doesn't say anything about overflow; it talks about other cases where UNDEFINED can be returned. > If the number of basic elements received exceeds the limits of the count parameter, then MPI_GET_COUNT set the value of count to MPI_UNDEFINED. > > I don't think we have to distinguish between "received" and "set by MPI_STATUS_SET_ELEMENTS[X], since this is intended to implement as generalized request receive which is still a form of a "receive". Aside from minor grammar quibbles, looks ok to me. -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ From jsquyres at [hidden] Thu Apr 14 13:16:51 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Thu, 14 Apr 2011 14:16:51 -0400 Subject: [Mpi3-bwcompat] Tomorrow's bwcompat meeting In-Reply-To: <226674496.1302803874824.JavaMail.nobody@jsj6wl004.webex.com> Message-ID: <030B5D86-DB84-4D71-817E-96FA6A2EE004@cisco.com> Use the webex info below so that we can live edit / share the document. Same bat time (1pm US Eastern), different bat channel (see URL below). See you then. Begin forwarded message: > From: Jeff Squyres > Date: April 14, 2011 1:57:54 PM EDT > To: jsquyres_at_[hidden] > Subject: (Forward to attendees) Meeting changed: MPI-3 Bwcompat webex > Reply-To: jsquyres_at_[hidden] > > **** You can forward this email invitation to attendees **** > > Hello , > > Jeff Squyres changed the meeting information. > > Topic: MPI-3 Bwcompat webex > Date: Friday, April 15, 2011 > Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00) > Meeting Number: 208 473 754 > Meeting Password: count > > > ------------------------------------------------------- > To join the online meeting (Now from mobile devices!) > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&PW=NZTI5ODIzNTUx&RT=MiMxMQ%3D%3D > 2. Enter your name and email address. > 3. Enter the meeting password: count > 4. Click "Join Now". > 5. Follow the instructions that appear on your screen. > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&PW=NZTI5ODIzNTUx&ORT=MiMxMQ%3D%3D > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres_at_[hidden] > 1-408-525 0971 > > To update this meeting to your calendar program (for example Microsoft Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&ICS=UMI&LD=1&RD=2&ST=1&SHA2=q6yLI/Bzup5bBABER/Tzyn4qA0TAjVN2mo3a2Xoqy98=&RT=MiMxMQ%3D%3D > > > WebEx will automatically setup Meeting Manager for Windows the first time you join a meeting. To save time, you can setup prior to the meeting by clicking this link: > https://cisco.webex.com/ciscosales/meetingcenter/mcsetup.php > > > > > http://www.webex.com > > CCP:+14085256800x208473754# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsquyres at [hidden] Fri Apr 15 12:04:42 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Fri, 15 Apr 2011 13:04:42 -0400 Subject: [Mpi3-bwcompat] Fwd: Tomorrow's bwcompat meeting In-Reply-To: <030B5D86-DB84-4D71-817E-96FA6A2EE004@cisco.com> Message-ID: <17BF11C2-08AF-4EA3-BE81-9D9CEFA31946@cisco.com> Don't forget to use the webex information below for both the call-in and the document-sharing-thingy. Dave and I are on the call, waiting for y'all. Begin forwarded message: > From: Jeff Squyres > Date: April 14, 2011 2:16:51 PM EDT > To: MPI-3 Backwards Compat WG > Subject: Tomorrow's bwcompat meeting > > Use the webex info below so that we can live edit / share the document. Same bat time (1pm US Eastern), different bat channel (see URL below). > > See you then. > > > Begin forwarded message: > >> From: Jeff Squyres >> Date: April 14, 2011 1:57:54 PM EDT >> To: jsquyres_at_[hidden] >> Subject: (Forward to attendees) Meeting changed: MPI-3 Bwcompat webex >> Reply-To: jsquyres_at_[hidden] >> >> **** You can forward this email invitation to attendees **** >> >> Hello , >> >> Jeff Squyres changed the meeting information. >> >> Topic: MPI-3 Bwcompat webex >> Date: Friday, April 15, 2011 >> Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00) >> Meeting Number: 208 473 754 >> Meeting Password: count >> >> >> ------------------------------------------------------- >> To join the online meeting (Now from mobile devices!) >> ------------------------------------------------------- >> 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&PW=NZTI5ODIzNTUx&RT=MiMxMQ%3D%3D >> 2. Enter your name and email address. >> 3. Enter the meeting password: count >> 4. Click "Join Now". >> 5. Follow the instructions that appear on your screen. >> >> To view in other time zones or languages, please click the link: >> https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&PW=NZTI5ODIzNTUx&ORT=MiMxMQ%3D%3D >> >> ---------------------------------------------------------------- >> ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes >> ---------------------------------------------------------------- >> >> The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area. >> >> Please dial the local access number for your area from the list below: >> - San Jose/Milpitas (408) area: 525-6800 >> - RTP (919) area: 392-3330 >> >> ------------------------------------------------------- >> To join the teleconference only >> ------------------------------------------------------- >> 1. Dial into Cisco WebEx (view all Global Access Numbers at >> http://cisco.com/en/US/about/doing_business/conferencing/index.html >> 2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign. >> >> San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 >> >> US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 >> >> India: +91.80.4350.1111 Germany: +49.619.6773.9002 >> >> Japan: +81.3.5763.9394 China: +86.10.8515.5666 >> >> ------------------------------------------------------- >> For assistance >> ------------------------------------------------------- >> 1. Go to https://cisco.webex.com/ciscosales/mc >> 2. On the left navigation bar, click "Support". >> >> You can contact me at: >> jsquyres_at_[hidden] >> 1-408-525 0971 >> >> To update this meeting to your calendar program (for example Microsoft Outlook), click this link: >> https://cisco.webex.com/ciscosales/j.php?ED=163291387&UID=0&ICS=UMI&LD=1&RD=2&ST=1&SHA2=q6yLI/Bzup5bBABER/Tzyn4qA0TAjVN2mo3a2Xoqy98=&RT=MiMxMQ%3D%3D >> >> >> WebEx will automatically setup Meeting Manager for Windows the first time you join a meeting. To save time, you can setup prior to the meeting by clicking this link: >> https://cisco.webex.com/ciscosales/meetingcenter/mcsetup.php >> >> >> >> >> http://www.webex.com >> >> CCP:+14085256800x208473754# >> >> IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. > > > -- > Jeff Squyres > jsquyres_at_[hidden] > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsquyres at [hidden] Wed Apr 20 06:45:13 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Wed, 20 Apr 2011 07:45:13 -0400 Subject: [Mpi3-bwcompat] Fwd: [Mpi-forum] Ticket reading and voting In-Reply-To: <11291389.1085.1303291009719.JavaMail.root@epsilon> Message-ID: <04668E48-24F7-441B-A514-189C17A9E031@cisco.com> I don't think we added a changelog entry, did we? Can someone go add one? Begin forwarded message: > From: Rolf Rabenseifner > Date: April 20, 2011 5:16:49 AM EDT > To: Main MPI Forum mailing list > Subject: [Mpi-forum] Ticket reading and voting > Reply-To: Main MPI Forum mailing list > > Dear ticket authors and reviewers, > > please note that a ticket is not ready for reading or voting > as long as it contains a new feature and has **no** entry > in the change-log. > Reviews not detecting such problems are incomplete reviews. > > I want only to remember, because in MPI-2.2 this caused > too many late changes. > > This is not only a formal rule, but it helps all implementors > to find all locations of needed work when implementing MPI-3.0, > especially those who cannot attend each Forum meeting. > > Tickets that contain a change-log-relevant new feature > should have me set as author (because I'm responsible > for the Change-log) and please, also my email in > the CC field of the ticket. > > Best regards > Rolf > > ----- Original Message ----- >> From: "RICHARD GRAHAM" >> To: mpi-forum_at_[hidden] >> Sent: Tuesday, April 19, 2011 5:10:42 PM >> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >> feel free just to respond to me - to my personal account. >> >> Thanks, >> Rich >> >>> Date: Tue, 19 Apr 2011 10:03:18 -0500 >>> From: balaji_at_[hidden] >>> To: mpi-forum_at_[hidden] >>> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >>> >>> >>> Me too. >>> >>> Why are we sending all these emails to the entire mailing list? >>> >>> -- Pavan >>> >>> On 04/19/2011 09:50 AM, Darius Buntinas wrote: >>>> me too! >>>> >>>> -d >>>> >>>> On Apr 19, 2011, at 9:24 AM, Jeff Squyres wrote: >>>> >>>>> I'll be attending. >>>>> >>>>> On Apr 19, 2011, at 10:18 AM, RICHARD GRAHAM wrote: >>>>> >>>>>> Just to let people know that it will be a while before the >>>>>> registration site is available. If you plan to attend, please >>>>>> send a note to the main mailing list, just so we can get a head >>>>>> count. >>>>>> >>>>>> Also, a reminder that next Monday, 4/25 is the last day to >>>>>> reserve a room at the Residence Inn at the government rate. >>>>>> >>>>>> Thanks, >>>>>> Rich >>>>>> _______________________________________________ >>>>>> mpi-forum mailing list >>>>>> mpi-forum_at_[hidden] >>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>> >>>>> >>>>> -- >>>>> Jeff Squyres >>>>> jsquyres_at_[hidden] >>>>> For corporate legal information go to: >>>>> http://www.cisco.com/web/about/doing_business/legal/cri/ >>>>> >>>>> >>>>> _______________________________________________ >>>>> mpi-forum mailing list >>>>> mpi-forum_at_[hidden] >>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>> >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum_at_[hidden] >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>> >>> -- >>> Pavan Balaji >>> http://www.mcs.anl.gov/~balaji >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum_at_[hidden] >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >> >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > mpi-forum mailing list > mpi-forum_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ From ftillier at [hidden] Wed Apr 20 13:08:03 2011 From: ftillier at [hidden] (Fab Tillier) Date: Wed, 20 Apr 2011 18:08:03 +0000 Subject: [Mpi3-bwcompat] Fwd: [Mpi-forum] Ticket reading and voting In-Reply-To: <04668E48-24F7-441B-A514-189C17A9E031@cisco.com> Message-ID: <91B583BE4B6FCD408F53D1B8F537E0921D7BE25E@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> Jeff Squyres wrote on Wed, 20 Apr 2011 at 04:45:13 > I don't think we added a changelog entry, did we? I don't think we did either. > Can someone go add one? I could edit the tex, but someone else would need to build a new PDF. -Fab > > > Begin forwarded message: > >> From: Rolf Rabenseifner >> Date: April 20, 2011 5:16:49 AM EDT >> To: Main MPI Forum mailing list >> Subject: [Mpi-forum] Ticket reading and voting >> Reply-To: Main MPI Forum mailing list >> >> Dear ticket authors and reviewers, >> >> please note that a ticket is not ready for reading or voting >> as long as it contains a new feature and has **no** entry >> in the change-log. >> Reviews not detecting such problems are incomplete reviews. >> >> I want only to remember, because in MPI-2.2 this caused >> too many late changes. >> >> This is not only a formal rule, but it helps all implementors >> to find all locations of needed work when implementing MPI-3.0, >> especially those who cannot attend each Forum meeting. >> >> Tickets that contain a change-log-relevant new feature >> should have me set as author (because I'm responsible >> for the Change-log) and please, also my email in >> the CC field of the ticket. >> >> Best regards >> Rolf >> >> ----- Original Message ----- >>> From: "RICHARD GRAHAM" >>> To: mpi-forum_at_[hidden] >>> Sent: Tuesday, April 19, 2011 5:10:42 PM >>> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >>> feel free just to respond to me - to my personal account. >>> >>> Thanks, >>> Rich >>> >>>> Date: Tue, 19 Apr 2011 10:03:18 -0500 >>>> From: balaji_at_[hidden] >>>> To: mpi-forum_at_[hidden] >>>> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >>>> >>>> >>>> Me too. >>>> >>>> Why are we sending all these emails to the entire mailing list? >>>> >>>> -- Pavan >>>> >>>> On 04/19/2011 09:50 AM, Darius Buntinas wrote: >>>>> me too! >>>>> >>>>> -d >>>>> >>>>> On Apr 19, 2011, at 9:24 AM, Jeff Squyres wrote: >>>>> >>>>>> I'll be attending. >>>>>> >>>>>> On Apr 19, 2011, at 10:18 AM, RICHARD GRAHAM wrote: >>>>>> >>>>>>> Just to let people know that it will be a while before the >>>>>>> registration site is available. If you plan to attend, please >>>>>>> send a note to the main mailing list, just so we can get a head >>>>>>> count. >>>>>>> >>>>>>> Also, a reminder that next Monday, 4/25 is the last day to >>>>>>> reserve a room at the Residence Inn at the government rate. >>>>>>> >>>>>>> Thanks, >>>>>>> Rich >>>>>>> _______________________________________________ >>>>>>> mpi-forum mailing list >>>>>>> mpi-forum_at_[hidden] >>>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>>> >>>>>> >>>>>> -- >>>>>> Jeff Squyres >>>>>> jsquyres_at_[hidden] >>>>>> For corporate legal information go to: >>>>>> http://www.cisco.com/web/about/doing_business/legal/cri/ >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> mpi-forum mailing list >>>>>> mpi-forum_at_[hidden] >>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>> >>>>> >>>>> _______________________________________________ >>>>> mpi-forum mailing list >>>>> mpi-forum_at_[hidden] >>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>> >>>> -- >>>> Pavan Balaji >>>> http://www.mcs.anl.gov/~balaji >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum_at_[hidden] >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum_at_[hidden] >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >> >> -- >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > From jsquyres at [hidden] Wed Apr 20 13:17:30 2011 From: jsquyres at [hidden] (Jeff Squyres) Date: Wed, 20 Apr 2011 14:17:30 -0400 Subject: [Mpi3-bwcompat] Fwd: [Mpi-forum] Ticket reading and voting In-Reply-To: <91B583BE4B6FCD408F53D1B8F537E0921D7BE25E@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> Message-ID: Send me a patch or commit to SVN and I'll make a new PDF. On Apr 20, 2011, at 2:08 PM, Fab Tillier wrote: > Jeff Squyres wrote on Wed, 20 Apr 2011 at 04:45:13 > >> I don't think we added a changelog entry, did we? > > I don't think we did either. > >> Can someone go add one? > > I could edit the tex, but someone else would need to build a new PDF. > > -Fab > >> >> >> Begin forwarded message: >> >>> From: Rolf Rabenseifner >>> Date: April 20, 2011 5:16:49 AM EDT >>> To: Main MPI Forum mailing list >>> Subject: [Mpi-forum] Ticket reading and voting >>> Reply-To: Main MPI Forum mailing list >>> >>> Dear ticket authors and reviewers, >>> >>> please note that a ticket is not ready for reading or voting >>> as long as it contains a new feature and has **no** entry >>> in the change-log. >>> Reviews not detecting such problems are incomplete reviews. >>> >>> I want only to remember, because in MPI-2.2 this caused >>> too many late changes. >>> >>> This is not only a formal rule, but it helps all implementors >>> to find all locations of needed work when implementing MPI-3.0, >>> especially those who cannot attend each Forum meeting. >>> >>> Tickets that contain a change-log-relevant new feature >>> should have me set as author (because I'm responsible >>> for the Change-log) and please, also my email in >>> the CC field of the ticket. >>> >>> Best regards >>> Rolf >>> >>> ----- Original Message ----- >>>> From: "RICHARD GRAHAM" >>>> To: mpi-forum_at_[hidden] >>>> Sent: Tuesday, April 19, 2011 5:10:42 PM >>>> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >>>> feel free just to respond to me - to my personal account. >>>> >>>> Thanks, >>>> Rich >>>> >>>>> Date: Tue, 19 Apr 2011 10:03:18 -0500 >>>>> From: balaji_at_[hidden] >>>>> To: mpi-forum_at_[hidden] >>>>> Subject: Re: [Mpi-forum] Next Meeting of the MPI Forum >>>>> >>>>> >>>>> Me too. >>>>> >>>>> Why are we sending all these emails to the entire mailing list? >>>>> >>>>> -- Pavan >>>>> >>>>> On 04/19/2011 09:50 AM, Darius Buntinas wrote: >>>>>> me too! >>>>>> >>>>>> -d >>>>>> >>>>>> On Apr 19, 2011, at 9:24 AM, Jeff Squyres wrote: >>>>>> >>>>>>> I'll be attending. >>>>>>> >>>>>>> On Apr 19, 2011, at 10:18 AM, RICHARD GRAHAM wrote: >>>>>>> >>>>>>>> Just to let people know that it will be a while before the >>>>>>>> registration site is available. If you plan to attend, please >>>>>>>> send a note to the main mailing list, just so we can get a head >>>>>>>> count. >>>>>>>> >>>>>>>> Also, a reminder that next Monday, 4/25 is the last day to >>>>>>>> reserve a room at the Residence Inn at the government rate. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Rich >>>>>>>> _______________________________________________ >>>>>>>> mpi-forum mailing list >>>>>>>> mpi-forum_at_[hidden] >>>>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Jeff Squyres >>>>>>> jsquyres_at_[hidden] >>>>>>> For corporate legal information go to: >>>>>>> http://www.cisco.com/web/about/doing_business/legal/cri/ >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> mpi-forum mailing list >>>>>>> mpi-forum_at_[hidden] >>>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> mpi-forum mailing list >>>>>> mpi-forum_at_[hidden] >>>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>>> >>>>> -- >>>>> Pavan Balaji >>>>> http://www.mcs.anl.gov/~balaji >>>>> _______________________________________________ >>>>> mpi-forum mailing list >>>>> mpi-forum_at_[hidden] >>>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum_at_[hidden] >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >>> >>> -- >>> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >>> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >>> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >>> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >>> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum_at_[hidden] >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >> >> > > _______________________________________________ > Mpi3-bwcompat mailing list > Mpi3-bwcompat_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/