From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steve Wise <swise@opengridcomputing.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma@vger.kernel.org, tom@ogc.us
Subject: Re: [PATCH] svcrdma: refactor marshalling logic
Date: Sat, 26 Apr 2014 12:43:36 -0400 [thread overview]
Message-ID: <20140426164336.GA11272@fieldses.org> (raw)
In-Reply-To: <6B12FA09-0E8C-497A-9145-E2B7CAB16C53@oracle.com>
On Fri, Apr 25, 2014 at 09:24:47AM -0400, Chuck Lever wrote:
> Hi Bruce-
>
> On Apr 25, 2014, at 6:58 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
>
> > On Thu, Apr 10, 2014 at 01:37:23PM -0500, Steve Wise wrote:
> >> From: Tom Tucker <tom@ogc.us>
> >>
> >> This patch refactors the 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.
> >>
> >> Signed-off-by: Tom Tucker <tom@ogc.us>
> >> ---
> >>
> >> include/linux/sunrpc/svc_rdma.h | 3
> >> net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 551 +++++++++---------------------
> >> net/sunrpc/xprtrdma/svc_rdma_sendto.c | 230 +------------
> >> net/sunrpc/xprtrdma/svc_rdma_transport.c | 57 ++-
> >> 4 files changed, 222 insertions(+), 619 deletions(-)
> >
> > Is it possible to make this change in more than one step?
> >
> > RDMA is pretty esoteric to most of us, so honestly this will probably
> > get merged based just on your having tested it, but if it was possible
> > to break this up into smaller patches you might give us at least a
> > fighting chance of giving it some review….
>
> I agree it could be broken up.
>
> However, my testing revealed that the patch inadvertently breaks support
> for HCAs that do not support FRMR. I’ve reported this to Steve and Tom.
> IMO you should wait for a newer version of the refactoring patch.
Great, thanks, I'll wait.
> There are plenty of people who can review and test these patches. We are
> working on setting up regular testing in a broad array of environments.
>
> In general it would be best for maintainers not to merge NFS/RDMA patches
> at least until you see Tested-by and/or Reviewed-by on the mailing
> list.
(which note this had).
> I
> also thought it was appropriate to mail patches To: you when they are ready
> to be merged, but To: the mailing lists when asking for review. Will that
> be a problem?
It'd be clearer to add an [RFC ...] or say clearly in the email that
it's not meant to be applied yet.
--b.
prev parent reply other threads:[~2014-04-26 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 18:37 [PATCH] svcrdma: refactor marshalling logic Steve Wise
2014-04-17 17:59 ` Steve Wise
2014-04-18 14:36 ` Steve Wise
2014-04-25 10:58 ` J. Bruce Fields
2014-04-25 13:24 ` Chuck Lever
2014-04-25 13:34 ` Steve Wise
2014-04-26 16:43 ` J. Bruce Fields [this message]
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=20140426164336.GA11272@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=swise@opengridcomputing.com \
--cc=tom@ogc.us \
/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).