diff options
author | Hans Westgaard Ry <hans.westgaard.ry@oracle.com> | 2016-10-28 13:14:29 +0200 |
---|---|---|
committer | Doug Ledford <dledford@redhat.com> | 2016-12-14 12:56:24 -0500 |
commit | 9315bc9a133011fdb084f2626b86db3ebb64661f (patch) | |
tree | e9e20f7b8ad158e90b22a14aa195c16dccbe33e3 /Documentation/phy | |
parent | 24dc08c3c9891a79f2754f99b7bffe65745af0f3 (diff) | |
download | linux-9315bc9a133011fdb084f2626b86db3ebb64661f.tar.bz2 |
IB/core: Issue DREQ when receiving REQ/REP for stale QP
from "InfiBand Architecture Specifications Volume 1":
A QP is said to have a stale connection when only one side has
connection information. A stale connection may result if the remote CM
had dropped the connection and sent a DREQ but the DREQ was never
received by the local CM. Alternatively the remote CM may have lost
all record of past connections because its node crashed and rebooted,
while the local CM did not become aware of the remote node's reboot
and therefore did not clean up stale connections.
and:
A local CM may receive a REQ/REP for a stale connection. It shall
abort the connection issuing REJ to the REQ/REP. It shall then issue
DREQ with "DREQ:remote QPN” set to the remote QPN from the REQ/REP.
This patch solves a problem with reuse of QPN. Current codebase, that
is IPoIB, relies on a REAP-mechanism to do cleanup of the structures
in CM. A problem with this is the timeconstants governing this
mechanism; they are up to 768 seconds and the interface may look
inresponsive in that period. Issuing a DREQ (and receiving a DREP)
does the necessary cleanup and the interface comes up.
Signed-off-by: Hans Westgaard Ry <hans.westgaard.ry@oracle.com>
Reviewed-by: Håkon Bugge <haakon.bugge@oracle.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'Documentation/phy')
0 files changed, 0 insertions, 0 deletions