From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please Pull NFSoRDMA Client Side Changes for 4.5
Date: Fri, 18 Dec 2015 15:44:45 -0500 [thread overview]
Message-ID: <5674703D.4050001@Netapp.com> (raw)
Hi Trond,
The following changes since commit 9f9499ae8e6415cefc4fe0a96ad0e27864353c89:
Linux 4.4-rc5 (2015-12-13 17:42:58 -0800)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/nfs-rdma.git tags/nfs-rdma-4.5
for you to fetch changes up to 26ae9d1c5af1b1d669ca1c28fc02bbca3d778d45:
xprtrdma: Revert commit e7104a2a9606 ('xprtrdma: Cap req_cqinit'). (2015-12-18 15:34:33 -0500)
Thanks,
Anna
----------------------------------------------------------------
Chuck Lever (10):
xprtrdma: Fix additional uses of spin_lock_irqsave(rb_lock)
xprtrdma: xprt_rdma_free() must not release backchannel reqs
xprtrdma: Disable RPC/RDMA backchannel debugging messages
xprtrdma: Move struct ib_send_wr off the stack
xprtrdma: Introduce ro_unmap_sync method
xprtrdma: Add ro_unmap_sync method for FRWR
xprtrdma: Add ro_unmap_sync method for FMR
xprtrdma: Add ro_unmap_sync method for all-physical registration
xprtrdma: Invalidate in the RPC reply handler
xprtrdma: Revert commit e7104a2a9606 ('xprtrdma: Cap req_cqinit').
Dan Carpenter (2):
xprtrdma: clean up some curly braces
xprtrdma: checking for NULL instead of IS_ERR()
net/sunrpc/xprtrdma/backchannel.c | 26 ++++++-------
net/sunrpc/xprtrdma/fmr_ops.c | 64 +++++++++++++++++++++++++++++++
net/sunrpc/xprtrdma/frwr_ops.c | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------
net/sunrpc/xprtrdma/physical_ops.c | 13 +++++++
net/sunrpc/xprtrdma/rpc_rdma.c | 16 ++++++++
net/sunrpc/xprtrdma/transport.c | 3 ++
net/sunrpc/xprtrdma/verbs.c | 16 ++++----
net/sunrpc/xprtrdma/xprt_rdma.h | 14 ++++---
8 files changed, 275 insertions(+), 51 deletions(-)
reply other threads:[~2015-12-18 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5674703D.4050001@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox