All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 9 Jul 2014 14:52:00 -0500	[thread overview]
Message-ID: <00be01cf9baf$3f68f960$be3aec20$@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-rc4 and has these additional patches:

Chuck Lever (21):
      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

Hariprasad S (2):
      iw_cxgb4: Fix skb_leak in reject_cr
      iw_cxgb4: clean up connection on arp error

Jan Beulich (1):
      x86-64: fix vDSO build

Steve Wise (3):
      iw_cxgb4: call iwpm_init() only once
      iw_cxgb4: initialize the device status page
      svcrdma: send_write() must not overflow the device's max sge


Cheers,

Steve.


WARNING: multiple messages have this Message-ID (diff)
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	'Shirley Ma' <shirley.ma-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	'Chuck Lever'
	<chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	"'Veeresh U. Kokatnur'"
	<veereshuk-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>,
	'Indranil Choudhury'
	<indranil-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: NFSRDMA test branch update
Date: Wed, 9 Jul 2014 14:52:00 -0500	[thread overview]
Message-ID: <00be01cf9baf$3f68f960$be3aec20$@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-rc4 and has these additional patches:

Chuck Lever (21):
      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

Hariprasad S (2):
      iw_cxgb4: Fix skb_leak in reject_cr
      iw_cxgb4: clean up connection on arp error

Jan Beulich (1):
      x86-64: fix vDSO build

Steve Wise (3):
      iw_cxgb4: call iwpm_init() only once
      iw_cxgb4: initialize the device status page
      svcrdma: send_write() must not overflow the device's max sge


Cheers,

Steve.

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-07-09 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 19:52 Steve Wise [this message]
2014-07-09 19:52 ` NFSRDMA test branch update Steve Wise

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='00be01cf9baf$3f68f960$be3aec20$@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 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.