All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org,
	"Veeresh U. Kokatnur" <veereshuk@chelsio.com>
Subject: Re: [PATCH v2 0/2] NFS/RDMA server patches for 3.17
Date: Tue, 15 Jul 2014 15:46:24 -0500	[thread overview]
Message-ID: <53C59320.70904@opengridcomputing.com> (raw)
In-Reply-To: <20140715175144.3448.48674.stgit@klimt.1015granger.net>

On 7/15/2014 12:54 PM, Chuck Lever wrote:
> Hi Steve-
>
> Can you include these 3.17 candidate patches in your testing branch?
>
> v2:
>
> - Second patch replaced with a lower-level fix
>

Done.

The for-test branch of git://git.linux-nfs.org/projects/swise/linux.git 
is now based on 3.16-rc5 plus:

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

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

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


WARNING: multiple messages have this Message-ID (diff)
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Veeresh U. Kokatnur"
	<veereshuk-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH v2 0/2] NFS/RDMA server patches for 3.17
Date: Tue, 15 Jul 2014 15:46:24 -0500	[thread overview]
Message-ID: <53C59320.70904@opengridcomputing.com> (raw)
In-Reply-To: <20140715175144.3448.48674.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>

On 7/15/2014 12:54 PM, Chuck Lever wrote:
> Hi Steve-
>
> Can you include these 3.17 candidate patches in your testing branch?
>
> v2:
>
> - Second patch replaced with a lower-level fix
>

Done.

The for-test branch of git://git.linux-nfs.org/projects/swise/linux.git 
is now based on 3.16-rc5 plus:

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

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

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

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

  parent reply	other threads:[~2014-07-15 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 17:54 [PATCH v2 0/2] NFS/RDMA server patches for 3.17 Chuck Lever
2014-07-15 17:54 ` Chuck Lever
2014-07-15 17:54 ` [PATCH v2 1/2] svcrdma: Increase credit limit to 32 Chuck Lever
2014-07-15 17:54   ` Chuck Lever
2014-07-15 17:55 ` [PATCH v2 2/2] svcrdma: Add zero padding if the client doesn't send it Chuck Lever
2014-07-15 17:55   ` Chuck Lever
2014-07-15 20:46 ` Steve Wise [this message]
2014-07-15 20:46   ` [PATCH v2 0/2] NFS/RDMA server patches for 3.17 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=53C59320.70904@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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.