From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
Cc: Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tom-/Yg/VP3ZvrM@public.gmane.org
Subject: Re: [PATCH] svcrdma: refactor marshalling logic
Date: Fri, 25 Apr 2014 08:34:46 -0500 [thread overview]
Message-ID: <535A6476.8080207@opengridcomputing.com> (raw)
In-Reply-To: <6B12FA09-0E8C-497A-9145-E2B7CAB16C53-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On 4/25/2014 8:24 AM, Chuck Lever wrote:
> Hi Bruce-
>
> On Apr 25, 2014, at 6:58 AM, J. Bruce Fields <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org> wrote:
>
>> On Thu, Apr 10, 2014 at 01:37:23PM -0500, Steve Wise wrote:
>>> From: Tom Tucker <tom-/Yg/VP3ZvrM@public.gmane.org>
>>>
>>> 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-/Yg/VP3ZvrM@public.gmane.org>
>>> ---
>>>
>>> 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.
I'll figure out the regression, and work with tom to repost this as a
series.
Steve.
--
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
next prev parent reply other threads:[~2014-04-25 13:34 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
[not found] ` <20140410183723.29724.18665.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2014-04-17 17:59 ` Steve Wise
2014-04-18 14:36 ` Steve Wise
2014-04-25 10:58 ` J. Bruce Fields
[not found] ` <20140425105838.GE22295-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2014-04-25 13:24 ` Chuck Lever
[not found] ` <6B12FA09-0E8C-497A-9145-E2B7CAB16C53-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-04-25 13:34 ` Steve Wise [this message]
2014-04-26 16:43 ` J. Bruce Fields
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=535A6476.8080207@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tom-/Yg/VP3ZvrM@public.gmane.org \
/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