All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
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, 06 May 2014 16:09:06 -0500	[thread overview]
Message-ID: <53694F72.9010007@opengridcomputing.com> (raw)
In-Reply-To: <20140506192730.GK18281@fieldses.org>

On 5/6/2014 2:27 PM, J. Bruce Fields wrote:
> 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.

I didn't see a good way to split it up, have it bisectable, and not have 
all the big stuff in one patch.  I think its a little more reviewable in 
these 3 patches, but when I post V3, I'll put it back as an uber patch.  
Hopefully folks can have a look at these 3 patches ignoring the bisect 
issue.    Having said that, the rdma read logic really is better 
reviewed by look at the code after applying the patches.   That's why I 
published a git branch.

Thanks!

Steve.


WARNING: multiple messages have this Message-ID (diff)
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org
Subject: Re: [PATCH V2 RFC 0/3] svcrdma: refactor marshalling logic
Date: Tue, 06 May 2014 16:09:06 -0500	[thread overview]
Message-ID: <53694F72.9010007@opengridcomputing.com> (raw)
In-Reply-To: <20140506192730.GK18281-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>

On 5/6/2014 2:27 PM, J. Bruce Fields wrote:
> 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.

I didn't see a good way to split it up, have it bisectable, and not have 
all the big stuff in one patch.  I think its a little more reviewable in 
these 3 patches, but when I post V3, I'll put it back as an uber patch.  
Hopefully folks can have a look at these 3 patches ignoring the bisect 
issue.    Having said that, the rdma read logic really is better 
reviewed by look at the code after applying the patches.   That's why I 
published a git branch.

Thanks!

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-05-06 21:09 UTC|newest]

Thread overview: 40+ 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 ` Steve Wise
2014-05-06 17:46 ` [PATCH V2 RFC 1/3] svcrdma: Transport and header file changes Steve Wise
2014-05-06 17:46   ` Steve Wise
2014-05-06 19:21   ` J. Bruce Fields
2014-05-06 19:21     ` J. Bruce Fields
2014-05-06 21:02     ` Steve Wise
2014-05-06 21:02       ` Steve Wise
2014-05-06 21:13       ` J. Bruce Fields
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-06 17:46   ` Steve Wise
2014-05-13 18:22   ` Chuck Lever
2014-05-13 18:22     ` Chuck Lever
2014-05-13 20:37     ` Steve Wise
2014-05-13 20:37       ` Steve Wise
2014-05-13 21:44       ` Chuck Lever
2014-05-13 21:44         ` Chuck Lever
2014-05-14 14:26         ` Steve Wise
2014-05-14 14:26           ` Steve Wise
2014-05-14 14:39           ` Chuck Lever
2014-05-14 14:39             ` Chuck Lever
2014-05-14 18:11             ` Steve Wise
2014-05-14 18:11               ` Steve Wise
2014-05-14 18:21               ` Chuck Lever
2014-05-14 18:21                 ` Chuck Lever
2014-05-14 18:24                 ` Steve Wise
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 17:46   ` Steve Wise
2014-05-06 19:27 ` [PATCH V2 RFC 0/3] svcrdma: refactor marshalling logic J. Bruce Fields
2014-05-06 19:27   ` J. Bruce Fields
2014-05-06 21:09   ` Steve Wise [this message]
2014-05-06 21:09     ` Steve Wise
2014-05-19 19:07     ` Devesh Sharma
2014-05-19 19:07       ` Devesh Sharma
2014-05-19 19:14       ` Steve Wise
2014-05-19 19:14         ` Steve Wise
2014-05-20  5:42         ` Devesh Sharma
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=53694F72.9010007@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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 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.