[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mpi-21] Call for MPI 2.2 and 3.0 agenda items for the Jan meeting
- To: "mpi-21@xxxxxxxxxxxxx" <mpi-21@xxxxxxxxxxxxx>
- Subject: Re: [mpi-21] Call for MPI 2.2 and 3.0 agenda items for the Jan meeting
- From: Richard Graham <rlgraham@xxxxxxxx>
- Date: Sat, 01 Dec 2007 13:30:08 -0500
- Delivered-to: mpifrm-mpi-21-outgoing@mailbouncer.mcs.anl.gov
- Delivered-to: mpifrm-mpi-21@mailbouncer.mcs.anl.gov
- In-reply-to: <B88C1D09-63FA-4D97-82BC-FBC23B31EC62@osl.iu.edu>
- Reply-to: mpi-21@xxxxxxxxxxxxx
- Sender: owner-mpi-21@xxxxxxxxxxxxx
- Thread-index: Acg0SDMecXJb1qA7EdylTgAX8sZF7g==
- Thread-topic: [mpi-21] Call for MPI 2.2 and 3.0 agenda items for the Jan meeting
- User-agent: Microsoft-Entourage/11.3.6.070618
On 11/30/07 6:56 PM, "Douglas Gregor" <dgregor@xxxxxxxxxx> wrote:
>
> On Nov 30, 2007, at 11:26 AM, Richard Graham wrote:
>
>> This is a call for items to be included on the agenda for the Jan
>> meeting of
>> the MPI Forum. These should be items that people want to consider
>> for the
>> 2.2 and 3.0 (we have not agreed on what these will be called)
>> version of the
>> MPI standard.
>>
>> As before, what these need to be are real proposals, i.e. we need
>> to have a
>> solid proposal for the change/addition being proposed, with pros
>> and cons.
>
> Is there any particular form that these proposal should take, or
> perhaps an existing proposal to use as a pattern for new proposals?
>
>> 3.0
>> ***
>> - Revamped one-sided communications
>> - Improved support for generalized requests
>> - Non-blocking collectives
>> - New support for process fault tolerance
>> - Sub-setting functionality
>
> We'll be proposing:
> - support receiving messages of unknown length
I think that what you will need to address here is why not use the probe or
iprobe functionality for this, as this is a way within the current standard
to do this. There may be very good reasons not to do this, but this would
be my first question. You may have already thought about this, and I may
have misunderstood what you mean.
Rich
>
> - Doug
>