From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@osdl.org>
Cc: Bret Towe <magnade@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: nfs udp 1000/100baseT issue
Date: Fri, 17 Mar 2006 10:53:25 -0500 [thread overview]
Message-ID: <1142610805.4250.7.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060317031834.43d3c1e6.akpm@osdl.org>
On Fri, 2006-03-17 at 03:18 -0800, Andrew Morton wrote:
> "Bret Towe" <magnade@gmail.com> wrote:
> >
> > ive seen this on kernels as far back as 2.6.13 on my own machines
> > (was around that time when i accutally got gigabit at home)
> > and recently noticed on some thin clients i maintain that 2.4 kernels
> > on the client side are also affected so perhaps its server side issue?
> > as all servers ive seen this on are 2.6 i havent used 2.4 kernels in ages
> > on my own machines so i havent looked into if 2.4 has that issue server side
> > or not
>
> It would be interesting if you could do so. I do recall that
> nfs-over-crappy-udp was much better behaved in 2.4...
The 2.6 servers allow clients to use 32k block sizes for READ and WRITE
requests, and set that as the preferred size for both TCP and UDP. In
2.4, they only supported 8k blocks.
Cheers,
Trond
prev parent reply other threads:[~2006-03-17 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 22:24 Bret Towe
2006-03-16 20:41 ` Jan Engelhardt
2006-03-17 1:33 ` Bret Towe
2006-03-17 2:20 ` Neil Brown
2006-03-17 3:11 ` Bret Towe
2006-03-17 3:41 ` Neil Brown
2006-03-17 4:13 ` Lee Revell
2006-03-17 9:13 ` Helge Hafting
2006-03-17 11:18 ` Andrew Morton
2006-03-17 15:53 ` Trond Myklebust [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=1142610805.4250.7.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.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
all inboxes | Powered by JetHome®