summaryrefslogtreecommitdiff
path: root/CREDITS
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2014-07-29 21:24:45 (GMT)
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2014-07-31 20:22:55 (GMT)
commit9f9d802a28a107937ecda4ff78de2ab5cedd439d (patch)
treea531564f760c2113587a8aaec5fd864b32037f2d /CREDITS
parentc2922c0235aac1c787fa81e24d7d7e93c2202275 (diff)
downloadlinux-9f9d802a28a107937ecda4ff78de2ab5cedd439d.tar.xz
xprtrdma: Reset FRMRs when FAST_REG_MR is flushed by a disconnect
FAST_REG_MR Work Requests update a Memory Region's rkey. Rkey's are used to block unwanted access to the memory controlled by an MR. The rkey is passed to the receiver (the NFS server, in our case), and is also used by xprtrdma to invalidate the MR when the RPC is complete. When a FAST_REG_MR Work Request is flushed after a transport disconnect, xprtrdma cannot tell whether the WR actually hit the adapter or not. So it is indeterminant at that point whether the existing rkey is still valid. After the transport connection is re-established, the next FAST_REG_MR or LOCAL_INV Work Request against that MR can sometimes fail because the rkey value does not match what xprtrdma expects. The only reliable way to recover in this case is to deregister and register the MR before it is used again. These operations can be done only in a process context, so handle it in the transport connect worker. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Tested-by: Steve Wise <swise@opengridcomputing.com> Tested-by: Shirley Ma <shirley.ma@oracle.com> Tested-by: Devesh Sharma <devesh.sharma@emulex.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions