From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v3 06/21] xprtrdma: Don't invalidate FRMRs if registration fails
Date: Tue, 15 Jul 2014 10:21:04 -0400 [thread overview]
Message-ID: <20140715142104.8908.98112.stgit@manet.1015granger.net> (raw)
In-Reply-To: <20140715142020.8908.80969.stgit@manet.1015granger.net>
If FRMR registration fails, it's likely to transition the QP to the
error state. Or, registration may have failed because the QP is
_already_ in ERROR.
Thus calling rpcrdma_deregister_external() in
rpcrdma_create_chunks() is useless in FRMR mode: the LOCAL_INVs just
get flushed.
It is safe to leave existing registrations: when FRMR registration
is tried again, rpcrdma_register_frmr_external() checks if each FRMR
is already/still VALID, and knocks it down first if it is.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Tested-by: Steve Wise <swise@opengridcomputing.com>
---
net/sunrpc/xprtrdma/rpc_rdma.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/sunrpc/xprtrdma/rpc_rdma.c b/net/sunrpc/xprtrdma/rpc_rdma.c
index 54422f7..6166c98 100644
--- a/net/sunrpc/xprtrdma/rpc_rdma.c
+++ b/net/sunrpc/xprtrdma/rpc_rdma.c
@@ -271,9 +271,11 @@ rpcrdma_create_chunks(struct rpc_rqst *rqst, struct xdr_buf *target,
return (unsigned char *)iptr - (unsigned char *)headerp;
out:
- for (pos = 0; nchunks--;)
- pos += rpcrdma_deregister_external(
- &req->rl_segments[pos], r_xprt);
+ if (r_xprt->rx_ia.ri_memreg_strategy != RPCRDMA_FRMR) {
+ for (pos = 0; nchunks--;)
+ pos += rpcrdma_deregister_external(
+ &req->rl_segments[pos], r_xprt);
+ }
return n;
}
next prev parent reply other threads:[~2014-07-15 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 14:20 [PATCH v3 01/21] xprtrdma: Fix panic in rpcrdma_register_frmr_external() Chuck Lever
2014-07-15 14:20 ` [PATCH v3 02/21] xprtrdma: Protect ia->ri_id when unmapping/invalidating MRs Chuck Lever
2014-07-15 14:20 ` [PATCH v3 03/21] xprtrdma: Limit data payload size for ALLPHYSICAL Chuck Lever
2014-07-15 14:20 ` [PATCH v3 04/21] xprtrdma: Update rkeys after transport reconnect Chuck Lever
2014-07-15 14:20 ` [PATCH v3 05/21] xprtrdma: On disconnect, don't ignore pending CQEs Chuck Lever
2014-07-15 14:21 ` Chuck Lever [this message]
2014-07-15 14:21 ` [PATCH v3 07/21] xprtrdma: Unclutter struct rpcrdma_mr_seg Chuck Lever
2014-07-15 14:21 ` [PATCH v3 08/21] xprtrdma: Back off rkey when FAST_REG_MR fails Chuck Lever
2014-07-15 14:21 ` [PATCH v3 09/21] xprtrdma: Chain together all MWs in same buffer pool Chuck Lever
2014-07-15 14:21 ` [PATCH v3 10/21] xprtrdma: Properly handle exhaustion of the rb_mws list Chuck Lever
2014-07-15 14:21 ` [PATCH v3 11/21] xprtrdma: Reset FRMRs when FAST_REG_MR is flushed by a disconnect Chuck Lever
2014-07-15 14:21 ` [PATCH v3 12/21] xprtrdma: Reset FRMRs after a flushed LOCAL_INV Work Request Chuck Lever
2014-07-15 14:22 ` [PATCH v3 13/21] xprtrdma: Don't post a LOCAL_INV in rpcrdma_register_frmr_external() Chuck Lever
2014-07-15 14:22 ` [PATCH v3 14/21] xprtrdma: Disable completions for FAST_REG_MR Work Requests Chuck Lever
2014-07-15 14:22 ` [PATCH v3 15/21] xprtrdma: Disable completions for LOCAL_INV " Chuck Lever
2014-07-15 14:22 ` [PATCH v3 16/21] xprtrdma: Rename frmr_wr Chuck Lever
2014-07-15 14:22 ` [PATCH v3 17/21] xprtrdma: Allocate each struct rpcrdma_mw separately Chuck Lever
2014-07-15 14:22 ` [PATCH v3 18/21] xprtrdma: Schedule reply tasklet once per upcall Chuck Lever
2014-07-15 14:22 ` [PATCH v3 19/21] xprtrdma: Make rpcrdma_ep_disconnect() return void Chuck Lever
2014-07-15 14:23 ` [PATCH v3 20/21] xprtrdma: Remove RPCRDMA_PERSISTENT_REGISTRATION macro Chuck Lever
2014-07-15 14:23 ` [PATCH v3 21/21] xprtrdma: Handle additional connection events Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140715142104.8908.98112.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox