From: Steve Dickson <SteveD@redhat.com>
To: Max Matveev <makc@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Ben England <bengland@redhat.com>
Subject: Re: [PATCH] RDMA: Increasing RPCRDMA_MAX_DATA_SEGS
Date: Mon, 25 Jul 2011 11:18:26 -0400 [thread overview]
Message-ID: <4E2D8942.9020602@RedHat.com> (raw)
In-Reply-To: <20009.12921.103429.724673@regina.usersys.redhat.com>
Sorry for the delayed response... I took a day off..
On 07/22/2011 04:19 AM, Max Matveev wrote:
> On Thu, 21 Jul 2011 13:49:02 -0400, Steve Dickson wrote:
>
> steved> Our performance team has noticed that increasing
> steved> RPCRDMA_MAX_DATA_SEGS from 8 to 64 significantly
> steved> increases throughput when using the RDMA transport.
>
> Did they try new client with old server and vice versa?
> Both read and write?
I believe it was done on the server side, but I've cc-ed the
person who did the testing....
steved.
prev parent reply other threads:[~2011-07-25 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 17:49 [PATCH] RDMA: Increasing RPCRDMA_MAX_DATA_SEGS Steve Dickson
2011-07-21 21:41 ` J. Bruce Fields
2011-07-22 1:42 ` Trond Myklebust
2011-07-22 1:55 ` J. Bruce Fields
2011-07-22 8:19 ` Max Matveev
2011-07-25 15:18 ` Steve Dickson [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=4E2D8942.9020602@RedHat.com \
--to=steved@redhat.com \
--cc=bengland@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=makc@redhat.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).