All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: anna.schumaker@netapp.com, trondmy@hammerspace.com
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v3 0/2] Fix write pad
Date: Tue, 05 Oct 2021 10:17:53 -0400	[thread overview]
Message-ID: <163344340514.1933.10783386394620857061.stgit@morisot.1015granger.net> (raw)

Hi Anna-

Can you include this series in your next pull request to Trond?

Trond, 

This series addresses your concern about xprtrdma using the 
rq_rcv_buf.tail vector in some cases to receive an XDR pad. It has
been tested with a legacy Solaris server, in addition to the usual
tests I run.

We haven't yet confirmed whether this addresses the GPU-Direct
issue, but since that is an out-of-tree user that depends on 
unsupported kernel facilities, I regard that confirmation as only
"nice to have", not mandatory. We are confident this change will
address that situation, based on our understanding of the issue.

Changes since v2:
- Address more review comments from Tom Talpey

---

Chuck Lever (2):
      xprtrdma: Provide a buffer to pad Write chunks of unaligned length
      xprtrdma: Remove rpcrdma_ep::re_implicit_roundup


 include/trace/events/rpcrdma.h  | 13 +++++++++---
 net/sunrpc/xprtrdma/frwr_ops.c  | 35 +++++++++++++++++++++++++++++++++
 net/sunrpc/xprtrdma/rpc_rdma.c  | 23 +++++++++++++---------
 net/sunrpc/xprtrdma/verbs.c     |  3 +--
 net/sunrpc/xprtrdma/xprt_rdma.h |  6 +++++-
 5 files changed, 65 insertions(+), 15 deletions(-)

--
Chuck Lever


             reply	other threads:[~2021-10-05 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 14:17 Chuck Lever [this message]
2021-10-05 14:17 ` [PATCH v3 1/2] xprtrdma: Provide a buffer to pad Write chunks of unaligned length Chuck Lever
2021-10-05 14:18 ` [PATCH v3 2/2] xprtrdma: Remove rpcrdma_ep::re_implicit_roundup 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=163344340514.1933.10783386394620857061.stgit@morisot.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=trondmy@hammerspace.com \
    /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.