All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/6] More xprtrdma fixes
Date: Mon, 05 Apr 2021 12:34:47 -0400	[thread overview]
Message-ID: <161764034907.29855.614994107807503843.stgit@manet.1015granger.net> (raw)

I found a number of crashers and other problems in the logic that
manages MR-related completions during disconnection events.

---

Chuck Lever (6):
      xprtrdma: rpcrdma_mr_pop() already does list_del_init()
      xprtrdma: Rename frwr_release_mr()
      xprtrdma: Clarify use of barrier in frwr_wc_localinv_done()
      xprtrdma: Do not recycle MR after FastReg/LocalInv flushes
      xprtrdma: Do not wake RPC consumer on a failed LocalInv
      xprtrdma: Avoid Send Queue wrapping


 include/trace/events/rpcrdma.h  |   1 -
 net/sunrpc/xprtrdma/frwr_ops.c  | 111 ++++++++++++++------------------
 net/sunrpc/xprtrdma/rpc_rdma.c  |  32 ++++++++-
 net/sunrpc/xprtrdma/verbs.c     |  20 +-----
 net/sunrpc/xprtrdma/xprt_rdma.h |   3 +-
 5 files changed, 82 insertions(+), 85 deletions(-)

--
Chuck Lever


             reply	other threads:[~2021-04-05 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 16:34 Chuck Lever [this message]
2021-04-05 16:34 ` [PATCH v1 1/6] xprtrdma: rpcrdma_mr_pop() already does list_del_init() Chuck Lever
2021-04-05 16:34 ` [PATCH v1 2/6] xprtrdma: Rename frwr_release_mr() Chuck Lever
2021-04-05 16:35 ` [PATCH v1 3/6] xprtrdma: Clarify use of barrier in frwr_wc_localinv_done() Chuck Lever
2021-04-05 16:35 ` [PATCH v1 4/6] xprtrdma: Do not recycle MR after FastReg/LocalInv flushes Chuck Lever
2021-04-05 16:35 ` [PATCH v1 5/6] xprtrdma: Do not wake RPC consumer on a failed LocalInv Chuck Lever
2021-04-05 16:35 ` [PATCH v1 6/6] xprtrdma: Avoid Send Queue wrapping 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=161764034907.29855.614994107807503843.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.