From: James Pearson <james-p@moving-picture.com>
To: linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: 2.6.0 NFS-server low to 0 performance
Date: Mon, 12 Jan 2004 14:40:25 +0000 [thread overview]
Message-ID: <4002B1D9.872714FE@moving-picture.com> (raw)
Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> På lau , 10/01/2004 klokka 11:08, skreiv Andi Kleen:
> > Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> >
> > > The correct solution to this problem is (b). I.e. we convert mount to
> > > use TCP as the default if it is available. That is consistent with what
> > > all other modern implementations do.
> >
> > Please do that. Fragmented UDP with 16bit ipid is just russian roulette at
> > today's network speeds.
>
> I fully agree.
>
> Chuck Lever recently sent an update for the NFS 'mount' utility to
> Andries. Among other things, that update changes this default. We're
> still waiting for his comments.
If mount defaults to trying TCP first then UDP if the TCP mount fails,
should there be separate options for [rw]size depending on what type of
mount actually takes place? e.g. 'ursize' and 'uwsize' for UDP and
'trsize' and 'twsize' for TCP ?
James Pearson
next reply other threads:[~2004-01-12 14:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 14:40 James Pearson [this message]
2004-01-12 15:22 ` 2.6.0 NFS-server low to 0 performance Trond Myklebust
2004-01-13 11:08 ` Muli Ben-Yehuda
[not found] <1cpDr-5az-11@gated-at.bofh.it>
[not found] ` <1csrv-Er-9@gated-at.bofh.it>
2004-01-10 16:08 ` Andi Kleen
2004-01-10 16:19 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 0:46 Guennadi Liakhovetski
2004-01-07 13:36 ` Guennadi Liakhovetski
2004-01-07 22:30 ` bill davidsen
2004-01-08 12:48 ` Guennadi Liakhovetski
2004-01-07 17:49 ` Mike Fedyk
2004-01-07 18:13 ` Guennadi Liakhovetski
2004-01-07 18:19 ` Mike Fedyk
2004-01-07 19:06 ` Guennadi Liakhovetski
2004-01-09 10:08 ` Guennadi Liakhovetski
2004-01-09 18:00 ` Mike Fedyk
2004-01-10 0:38 ` Guennadi Liakhovetski
2004-01-10 1:38 ` Mike Fedyk
2004-01-10 11:10 ` Guennadi Liakhovetski
2004-01-10 14:30 ` Trond Myklebust
2004-01-10 20:04 ` Guennadi Liakhovetski
2004-01-10 21:57 ` Trond Myklebust
2004-01-10 22:14 ` Mike Fedyk
2004-01-10 22:47 ` Trond Myklebust
2004-01-10 22:42 ` Guennadi Liakhovetski
2004-01-10 22:51 ` Jesper Juhl
2004-01-11 13:18 ` Helge Hafting
2004-01-11 13:53 ` Russell King
2004-01-11 14:24 ` Guennadi Liakhovetski
2004-01-15 11:38 ` Pavel Machek
2004-01-12 5:06 ` Bill Davidsen
2004-01-12 14:27 ` Trond Myklebust
2004-01-12 15:12 ` Trond Myklebust
2004-01-16 5:44 ` Mike Fedyk
2004-01-16 6:05 ` Trond Myklebust
2004-01-16 6:53 ` Mike Fedyk
2004-01-10 22:34 ` Mike Fedyk
2004-01-10 22:52 ` Guennadi Liakhovetski
2004-01-10 22:57 ` Mike Fedyk
2004-01-10 23:00 ` Guennadi Liakhovetski
2004-01-08 21:42 ` Pavel Machek
2004-01-12 23:18 ` Guennadi Liakhovetski
2004-01-12 23:28 ` Jesper Juhl
2004-01-13 0:39 ` Pavel Machek
2004-01-14 3:00 ` Daniel Roesen
2004-01-14 18:16 ` Guennadi Liakhovetski
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=4002B1D9.872714FE@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.