Hi,

In the the Windows user mode code for Windows Sockets Direct, it sends
a CM DREQ (ib_cm_dreq) and then just modifies the QP state to error,
forcing a flush of outstanding work items. Can someone explain this ?

Is this a workaround for a CM issue or the normal way to handle
connection termination ? Isn't the DREQ guaranteed to either have a DREP
reply event, or a timeout or error ? Who's responsibility is it to
assure that the QP is moved to an appropriate state (CM or "user"/ULP) ?

Thanks.

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

Reply via email to