From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/5] RPC/RDMA client connect-related fixes
Date: Wed, 23 Oct 2019 10:01:46 -0400 [thread overview]
Message-ID: <20191023135907.3992.69010.stgit@manet.1015granger.net> (raw)
First patch fixes a problem with the logic that deals with failure
to establish a connection. The others are trace point clean-ups that
I found along the way to the fix.
This is the final set of client patches I currently have ready for
the v5.5 merge window.
---
Chuck Lever (5):
xprtrdma: Wake tasks after connect worker fails
xprtrdma: Report the computed connect delay
xprtrdma: Refine trace_xprtrdma_fixup
xprtrdma: Replace dprintk() in rpcrdma_update_connect_private()
xprtrdma: Replace dprintk in xprt_rdma_set_port
include/trace/events/rpcrdma.h | 164 ++++++++++++++++++++++++---------------
net/sunrpc/xprtrdma/rpc_rdma.c | 9 --
net/sunrpc/xprtrdma/transport.c | 27 ++----
net/sunrpc/xprtrdma/verbs.c | 34 +++-----
4 files changed, 126 insertions(+), 108 deletions(-)
--
Chuck Lever
next reply other threads:[~2019-10-23 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 14:01 Chuck Lever [this message]
2019-10-23 14:01 ` [PATCH v1 1/5] xprtrdma: Wake tasks after connect worker fails Chuck Lever
2019-10-23 14:01 ` [PATCH v1 2/5] xprtrdma: Report the computed connect delay Chuck Lever
2019-10-23 14:02 ` [PATCH v1 3/5] xprtrdma: Refine trace_xprtrdma_fixup Chuck Lever
2019-10-23 14:02 ` [PATCH v1 4/5] xprtrdma: Replace dprintk() in rpcrdma_update_connect_private() Chuck Lever
2019-10-23 14:02 ` [PATCH v1 5/5] xprtrdma: Replace dprintk in xprt_rdma_set_port 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=20191023135907.3992.69010.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;
as well as URLs for NNTP newsgroup(s).