Bill,
we need to go wider then uDAPL.
The right folks to ask are UNH folks who run interop event.
Thanks,
 

Arkady Kanevsky                       email: [EMAIL PROTECTED]

Network Appliance Inc.               phone: 781-768-5395

1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195

Waltham, MA 02451                   central phone: 781-768-5300

 


________________________________

        From: Bill Boas [mailto:[EMAIL PROTECTED] 
        Sent: Wednesday, October 24, 2007 12:40 AM
        To: Arlin Davis
        Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
OpenFabrics General; [EMAIL PROTECTED]
        Subject: [ofa-general] Re: [Interop-wg] [RFP] support for iWARP
requirement -active connect side MUST send first FPDU
        
        
        All involved with iWARP and OFED contribution and maintenance
        
        Before the developer's session in Reno about iWARP, could you as
a team working together prepare a complete list of the iWARP technical
issues that confront everyone and the differences that you have with
each other in the current state of the implementation and diffrences you
have about resolving future isses you already have a sense of. 
        
        And publish that list before SC  with the options for
resolutions that have been pit forward so far. Arlin are you willing to
take the lead on accomplishing this?
        
        Is that a reasonable request so we can all understand and help
with the resolutions, if possible? 
        
        Bill.
        
        
        On 10/23/07, Arlin Davis <[EMAIL PROTECTED]> wrote: 


                There has been much discussion on a private thread
regarding bug #735 -
                "dapltest performance tests don't adhere to iWARP
standard" that needs
                to move to the general list.
                
                iWARP, has a requirement that the active side of the
connection MUST be 
                the first to send the first FPDU (SEND or RDMA
operation). This presents
                a problem with applications written for uDAPL and OFA
verbs given that
                there is no such restriction. So, short of requiring
every OFA
                application/ULP to adhere to this restriction, we need
the iWARP vendors 
                to come up with a standard method to remove the
restriction.
                
                Can someone come up with a solution, possibly in iWARP
CM, that will
                work and insure interoperability between iWARP devices?
                
                
                -arlin
                
                
                
                
                
                
                
                _______________________________________________
                Interop-wg mailing list
                [EMAIL PROTECTED]
        
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/interop-wg
                


_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to