From: Jim Rees <rees@umich.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] NFSv4.1: Convert slotid from u8 to u32
Date: Wed, 8 Feb 2012 15:31:40 -0500 [thread overview]
Message-ID: <20120208203140.GA29238@umich.edu> (raw)
In-Reply-To: <20120208183151.GA14316@fieldses.org>
J. Bruce Fields wrote:
On Wed, Feb 08, 2012 at 12:49:01PM -0500, Jim Rees wrote:
> Myklebust, Trond wrote:
>
> 10GigE + high latencies is exactly where we're seeing the value. Andy
> has been working with the high energy physics community doing NFS
> traffic between the US and CERN...
>
> CITI to CERN is just over 120ms. I don't know what it would be from Andy's
> house. Does he have 10G at home yet?
That still seems short of what you'd need to get a 255MB bandwidth-delay
product.
I'm just curious what the experiment is here and whether there's a
possibility the real problem is elsewhere.
In my opinion, any fix that involves allocating multiple parallel data
streams (rpc slots, tcp connections) is masking the real problem. But it's
an effective fix.
next prev parent reply other threads:[~2012-02-08 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 0:57 [RFC PATCH 1/2] NFSv4.1: Convert slotid from u8 to u32 Trond Myklebust
2012-02-07 0:57 ` [RFC PATCH 2/2] NFSv4.1: Add a module parameter to set the number of session slots Trond Myklebust
2012-02-08 7:34 ` [RFC PATCH 1/2] NFSv4.1: Convert slotid from u8 to u32 Benny Halevy
2012-02-08 16:23 ` J. Bruce Fields
2012-02-08 17:27 ` Myklebust, Trond
2012-02-08 17:49 ` Jim Rees
2012-02-08 18:31 ` J. Bruce Fields
2012-02-08 20:31 ` Jim Rees [this message]
2012-02-08 20:50 ` Myklebust, Trond
2012-02-08 21:01 ` Jim Rees
2012-02-09 8:37 ` Tigran Mkrtchyan
2012-02-09 18:39 ` J. Bruce Fields
2012-02-10 16:06 ` Andy Adamson
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=20120208203140.GA29238@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).