[dat-discussions] [openib-general] [RFC] DAT2.0immediatedataproposal

[Kanevsky, Arkady]

Arlin,
This can be done.

But I have an issue that extension call violate Transport Requirement.
Currently, the matching semantic is well-defined since
Recv only matches Send. Since Spec does not have any idea what
operations are defined in extension(s) there is a problem
with the transport requirements. We can, of course,
make some generic statement that with does not cover APIs
that are defined in extensions.

The API requirements are easier to handle. Since they have been
written as "Nonrequirement" for the APIs we decide to define yet.
(I will need to review chapter 5 to make we had followed this
in all cases.)

Arkady

Arkady Kanevsky                       email: arkady at netapp.com
Network Appliance Inc.               phone: 781-768-5395
1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195
Waltham, MA 02451                   central phone: 781-768-5300
 

> -----Original Message-----
> From: Arlin Davis [mailto:ardavis at ichips.intel.com] 
> Sent: Thursday, February 09, 2006 5:57 PM
> To: Michael Krause
> Cc: dat-discussions at yahoogroups.com; 
> openib-general at openib.org; Kanevsky, Arkady
> Subject: Re: [dat-discussions] [openib-general] [RFC] 
> DAT2.0immediatedataproposal
> 
> Michael Krause wrote:
> 
> > RDMA Write with Immediate is part of the IB Extended 
> Transport Header.  
> > It is a fixed-sized quantity and not one subject to change, i.e. 
> > increasing its size.
> >
> > Your argument above reinforces that the particular 
> application need is 
> > IB-specific and thus should not be part of a general API but a
> > transport-specific API.   If the application will only operate 
> > optimally using immediate data, then it is only suitable for an IB 
> > fabric.  This reinforces the need for a transport-specific API.
> 
> I agree. I will move the IB immediate data service back into 
> the extension interface and update the OpenIB uDAPL provider patch.
> 
> >
> > Those applications that simply want to enable completion 
> notification 
> > when a RDMA Write has occurred can use a general purpose 
> API that is 
> > interconnect independent and whose code is predicated upon a RDMA 
> > Write - Send set of operations.  This will enable application 
> > portability across all interconnect types.
> 
> I will defer this to Arkady to draft.
> 
> -arlin
>