All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Warnier" <jwarnier@beeznest.net>
To: nfs@lists.sourceforge.net
Subject: Re: NFS TCP settings
Date: Wed, 21 Dec 2005 23:05:50 +0100	[thread overview]
Message-ID: <1135202750.10000.23.camel@localhost> (raw)
In-Reply-To: <20051221163254.70779.qmail@web34105.mail.mud.yahoo.com>

Le mercredi 21 d=E9cembre 2005 =E0 08:32 -0800, Kenny Simpson a =E9crit :
> --- Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > The NFS/RPC code has no direct control over the TCP window size. That
> > would be an issue for the networking people.
>=20
> I have tracked this a bit further, and am reporting back for completeness=
..
>=20
> The version of OnTap we are using (6.4.1p1) does not seem to support RFC =
1323 (large TCP windows),
> but the Linux client does.  The window scaling is communicated in the ini=
tial connection (SYN), so
> if ethereal does not catch that, it will incorrectly report the window si=
ze as the unscaled number
> - making the Linux client appear to be using a very small window.
> The reason it appeared that the small window size was being honored is a =
result of the direct
> crossover cable making the BDP (bandwidth-delay product) very small.
>=20
> As for the server side, because large TCP windows are not supported, the =
best it can do is 64k -
> which it does.  Running with GbE and jumbo packets fills the window quite=
 fast obviating the need
> for RFC 1323.
I'm experiencing big performance trouble with NFS on a GbE NIC (Intel
eepro1000) and a 2.6.8 kernel, to the point of NFS being unusable, and
having to force NIC to 100Mbs. The clients are 10/100 Mbs.
I've made no particular tuning on the server side for the GbE. Could
someone help me to get the most out of this GbE NIC?

Thanks

> Thanks to those who took the time to swing a clue stick in my direction.
>=20
> -Kenny




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2005-12-21 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 15:38 NFS TCP settings Kenny Simpson
2005-12-20 15:47 ` Trond Myklebust
2005-12-21 16:32   ` Kenny Simpson
2005-12-21 19:02     ` Dan Stromberg
2005-12-22 22:41       ` Trond Myklebust
2005-12-21 22:05     ` Jérôme Warnier [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=1135202750.10000.23.camel@localhost \
    --to=jwarnier@beeznest.net \
    --cc=nfs@lists.sourceforge.net \
    /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.