From: Chuck Lever <chuck.lever@oracle.com>
To: Devesh Sharma <devesh.sharma@avagotech.com>
Cc: Tom Talpey <tom@talpey.com>,
linux-rdma@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 07/14] xprtrdma: Remove logic that constructs RDMA_MSGP type calls
Date: Wed, 15 Jul 2015 17:29:50 -0400 [thread overview]
Message-ID: <38D7020A-EF93-4545-A0BF-DF1C9645CA64@oracle.com> (raw)
In-Reply-To: <CANjDDBgLX9pBWv5Jt6YwMFhRULWgfjSJNOvwa8L6kwkykRbnRw@mail.gmail.com>
Thanks Devesh, will note that in the next versions of these series.
On Jul 15, 2015, at 2:26 PM, Devesh Sharma <devesh.sharma@avagotech.com> wrote:
> with MAX_IOVS set to 2 iozone passes with ocrdma device. My testing
> includes both the series of svcrdma and xprtrdma.
>
> On Wed, Jul 15, 2015 at 12:31 AM, Chuck Lever <chuck.lever@oracle.com> wrote:
>>
>> On Jul 14, 2015, at 3:00 PM, Tom Talpey <tom@talpey.com> wrote:
>>
>>> On 7/13/2015 12:30 PM, Chuck Lever wrote:
>>>> RDMA_MSGP type calls insert a zero pad in the middle of the RPC
>>>> message to align the RPC request's data payload to the server's
>>>> alignment preferences. A server can then "page flip" the payload
>>>> into place to avoid a data copy in certain circumstances. However:
>>>> ...
>>>>
>>>> Clean up the marshaling code by removing the logic that constructs
>>>> RDMA_MSGP type calls. This also reduces the maximum send iovec size
>>>> from four to just two elements.
>>>>
>>>
>>>> diff --git a/net/sunrpc/xprtrdma/xprt_rdma.h b/net/sunrpc/xprtrdma/xprt_rdma.h
>>>> index 8219011..0b50103 100644
>>>> --- a/net/sunrpc/xprtrdma/xprt_rdma.h
>>>> +++ b/net/sunrpc/xprtrdma/xprt_rdma.h
>>> ...>
>>>> +#define RPCRDMA_MAX_IOVS (4)
>>>> +
>>>
>>> So, shouldn't this constant be "2"? The extra 2 iov's were used
>>> only for constructing the pad.
>>
>> Yes, thanks. I folded a couple of patches together into this
>> one, and forgot to update the constant.
>>
>>
>> --
>> Chuck Lever
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
next prev parent reply other threads:[~2015-07-15 21:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 16:29 [PATCH v2 00/14] NFS/RDMA client side for Linux 4.3 Chuck Lever
2015-07-13 16:29 ` [PATCH v2 01/14] xprtrdma: Make xprt_setup_rdma() agnostic to family of server address Chuck Lever
2015-07-13 16:30 ` [PATCH v2 02/14] xprtrdma: Raise maximum payload size to one megabyte Chuck Lever
2015-07-13 16:30 ` [PATCH v2 03/14] xprtrdma: Increase default credit limit Chuck Lever
2015-07-13 16:30 ` [PATCH v2 04/14] xprtrdma: Don't fall back to PHYSICAL memory registration Chuck Lever
2015-07-13 16:30 ` [PATCH v2 05/14] xprtrdma: Remove last ib_reg_phys_mr() call site Chuck Lever
2015-07-13 16:30 ` [PATCH v2 06/14] xprtrdma: Clean up rpcrdma_ia_open() Chuck Lever
2015-07-13 16:30 ` [PATCH v2 07/14] xprtrdma: Remove logic that constructs RDMA_MSGP type calls Chuck Lever
2015-07-14 19:00 ` Tom Talpey
2015-07-14 19:01 ` Chuck Lever
2015-07-15 18:26 ` Devesh Sharma
2015-07-15 21:29 ` Chuck Lever [this message]
2015-07-13 16:30 ` [PATCH v2 08/14] xprtrdma: Account for RPC/RDMA header size when deciding to inline Chuck Lever
2015-07-13 16:31 ` [PATCH v2 09/14] xprtrdma: Always provide a write list when sending NFS READ Chuck Lever
2015-07-13 16:31 ` [PATCH v2 10/14] xprtrdma: Don't provide a reply chunk when expecting a short reply Chuck Lever
2015-07-13 16:31 ` [PATCH v2 11/14] xprtrdma: Fix XDR tail buffer marshalling Chuck Lever
2015-07-13 16:31 ` [PATCH v2 12/14] xprtrdma: Fix large NFS SYMLINK calls Chuck Lever
2015-07-13 16:31 ` [PATCH v2 13/14] xprtrdma: Clean up xprt_rdma_print_stats() Chuck Lever
2015-07-13 16:31 ` [PATCH v2 14/14] xprtrdma: Count RDMA_NOMSG type calls Chuck Lever
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=38D7020A-EF93-4545-A0BF-DF1C9645CA64@oracle.com \
--to=chuck.lever@oracle.com \
--cc=devesh.sharma@avagotech.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tom@talpey.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