From: "Steve Wise" <swise@opengridcomputing.com>
To: <linux-rdma@vger.kernel.org>
Cc: <linux-nfs@vger.kernel.org>,
"'Shirley Ma'" <shirley.ma@oracle.com>,
"'Chuck Lever'" <chuck.lever@oracle.com>,
"'Veeresh U. Kokatnur'" <veereshuk@chelsio.com>,
"'Indranil Choudhury'" <indranil@chelsio.com>
Subject: NFSRDMA test branch update to 3.16-rc6
Date: Tue, 22 Jul 2014 13:14:52 -0500 [thread overview]
Message-ID: <006601cfa5d8$d5331f10$7f995d30$@opengridcomputing.com> (raw)
Hey all,
I've updated the for-test branch of git://git.linux-nfs.org/projects/swise/linux.git. It
is based on tag v3.16-rc6 and has these additional patches including v4 of Chuck's client
series:
[swise@build linux]$ git shortlog v3.16-rc6.. stevo-nfs/for-test
Chuck Lever (23):
xprtrdma: Fix panic in rpcrdma_register_frmr_external()
xprtrdma: Protect ia->ri_id when unmapping/invalidating MRs
xprtrdma: Limit data payload size for ALLPHYSICAL
xprtrdma: Update rkeys after transport reconnect
xprtrdma: On disconnect, don't ignore pending CQEs
xprtrdma: Don't invalidate FRMRs if registration fails
xprtrdma: Unclutter struct rpcrdma_mr_seg
xprtrdma: Back off rkey when FAST_REG_MR fails
xprtrdma: Chain together all MWs in same buffer pool
xprtrdma: Properly handle exhaustion of the rb_mws list
xprtrdma: Reset FRMRs when FAST_REG_MR is flushed by a disconnect
xprtrdma: Reset FRMRs after a flushed LOCAL_INV Work Request
xprtrdma: Don't post a LOCAL_INV in rpcrdma_register_frmr_external()
xprtrdma: Disable completions for FAST_REG_MR Work Requests
xprtrdma: Disable completions for LOCAL_INV Work Requests
xprtrdma: Rename frmr_wr
xprtrdma: Allocate each struct rpcrdma_mw separately
xprtrdma: Schedule reply tasklet once per upcall
xprtrdma: Make rpcrdma_ep_disconnect() return void
xprtrdma: Remove RPCRDMA_PERSISTENT_REGISTRATION macro
xprtrdma: Handle additional connection events
[v2,1/2] svcrdma: Increase credit limit to 32
[v2,2/2] svcrdma: Add zero padding if the client doesn't send it
Steve Wise (1):
svcrdma: send_write() must not overflow the device's max sge
reply other threads:[~2014-07-22 18:14 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='006601cfa5d8$d5331f10$7f995d30$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=chuck.lever@oracle.com \
--cc=indranil@chelsio.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shirley.ma@oracle.com \
--cc=veereshuk@chelsio.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;
as well as URLs for NNTP newsgroup(s).