>
> 2) OMPI is not adhering to the iwarp protocol requirement
> that the ULP,
> in this case OMPI, initiating the iwarp connection (the side
> issuing the
> dat_ep_connect() or rdma_connect()) _MUST_ be the first to
> send an RDMA
> message. So if a OMPI process _accepts_ an rdma connection, the
Jeff Squyres wrote:
>
> - The other peer (the receiver of the connection) must wait
> to send its pending fragment(s) until it receives the first
> frag from the connection initiator. This can be accomplished
> either with another flag on the OMPI module struct or perhaps
> making it part of the
general-boun...@lists.openfabrics.org wrote:
>> Therefore, the only truly safe thing for an iWARP btl to do (or a
>> udapl btl since that is also an iWARP btl) is to have the active
>> layer send an MPI Layer "nop" of some kind immediately after
>> establishing the connection if there is nothing el
devel-boun...@open-mpi.org wrote:
> Steve Wise wrote:
>> There have been a series of discussions on the ofa general list about
>> this issue, and the conclusion to date is that it cannot be resolved
>> in the rdma-cm or iwarp-cm code of the linux rdma stack. Mainly
>> because sending an RDMA messa
general-boun...@lists.openfabrics.org wrote:
> On Wed, 2007-05-09 at 17:55 -0700, Andrew Friedley wrote:
>>
>> Steve Wise wrote:
>>> On Wed, 2007-05-09 at 16:15 -0700, Andrew Friedley wrote:
Steve Wise wrote:
> There have been a series of discussions on the ofa general list
> about th
devel-boun...@open-mpi.org wrote:
>> There are two new issues so far:
>>
>> 1) this has uncovered a connection migration issue in the Chelsio
>> driver/firmware. We are developing and testing a fix for this now.
>> Should be ready tomorrow hopefully.
>>
>
> I have a fix for the above issue and
Donal Kerr wrote:
>>> order of business after connection establishment
>>> (mba_btl_udapl_sendrecv(). The RECV buffer post for this exchange,
>>> however, should really be done _before_ the
>>> dat_ep_connect() on the active side, and _before_ the
>>> dat_cr_accept() on the server side.
>>> Curre
