linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Wise <swise@opengridcomputing.com>
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org,
	tom@opengridcomputing.com
Subject: Re: [PATCH V2 RFC 0/3] svcrdma: refactor marshalling logic
Date: Tue, 6 May 2014 15:27:30 -0400	[thread overview]
Message-ID: <20140506192730.GK18281@fieldses.org> (raw)
In-Reply-To: <20140506174621.18208.24242.stgit@build.ogc.int>

On Tue, May 06, 2014 at 12:46:21PM -0500, Steve Wise wrote:
> This patch series refactors the NFSRDMA server marshalling logic to
> remove the intermediary map structures.  It also fixes an existing bug
> where the NFSRDMA server was not minding the device fast register page
> list length limitations.
> 
> I've also made a git repo available with these patches on top of 3.15-rc4:
> 
> git://git.openfabrics.org/~swise/linux svcrdma-refactor
> 
> Changes since V1:
> 
> - fixed regression for devices that don't support FRMRs (see
>   rdma_read_chunk_lcl())
> 
> - split patch up for closer review.  However I request it be squashed
>   before merging as they is not bisectable, and I think these changes
>   should all be a single commit anyway.

If it's not split up in a way that's bisectable, then yes, just don't
bother.

--b.

> 
> Please review, and test if you can.
> 
> Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> 
> ---
> 
> Tom Tucker (3):
>       svcrdma: Sendto changes
>       svcrdma: Recvfrom changes
>       svcrdma: Transport and header file changes
> 
> 
>  include/linux/sunrpc/svc_rdma.h          |    3 
>  net/sunrpc/xprtrdma/svc_rdma_recvfrom.c  |  633 ++++++++++++------------------
>  net/sunrpc/xprtrdma/svc_rdma_sendto.c    |  230 +----------
>  net/sunrpc/xprtrdma/svc_rdma_transport.c |   62 ++-
>  4 files changed, 318 insertions(+), 610 deletions(-)
> 
> -- 
> 
> Steve / Tom

  parent reply	other threads:[~2014-05-06 19:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 17:46 [PATCH V2 RFC 0/3] svcrdma: refactor marshalling logic Steve Wise
2014-05-06 17:46 ` [PATCH V2 RFC 1/3] svcrdma: Transport and header file changes Steve Wise
2014-05-06 19:21   ` J. Bruce Fields
2014-05-06 21:02     ` Steve Wise
2014-05-06 21:13       ` J. Bruce Fields
2014-05-06 17:46 ` [PATCH V2 RFC 2/3] svcrdma: Recvfrom changes Steve Wise
2014-05-13 18:22   ` Chuck Lever
2014-05-13 20:37     ` Steve Wise
2014-05-13 21:44       ` Chuck Lever
2014-05-14 14:26         ` Steve Wise
2014-05-14 14:39           ` Chuck Lever
2014-05-14 18:11             ` Steve Wise
2014-05-14 18:21               ` Chuck Lever
2014-05-14 18:24                 ` Steve Wise
2014-05-06 17:46 ` [PATCH V2 RFC 3/3] svcrdma: Sendto changes Steve Wise
2014-05-06 19:27 ` J. Bruce Fields [this message]
2014-05-06 21:09   ` [PATCH V2 RFC 0/3] svcrdma: refactor marshalling logic Steve Wise
2014-05-19 19:07     ` Devesh Sharma
2014-05-19 19:14       ` Steve Wise
2014-05-20  5:42         ` Devesh Sharma

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=20140506192730.GK18281@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=swise@opengridcomputing.com \
    --cc=tom@opengridcomputing.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).