From: Andi Kleen <ak@muc.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 NFS-server low to 0 performance
Date: Sat, 10 Jan 2004 17:08:41 +0100 [thread overview]
Message-ID: <m3eku74whi.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1csrv-Er-9@gated-at.bofh.it> (Trond Myklebust's message of "Sat, 10 Jan 2004 15:40:09 +0100")
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.
One disadvantage is that some older (early 2.4) Linux nfsd servers that have
TCP enabled can cause problems. But I guess we can live with that, they
should be updated anyways.
-Andi
next parent reply other threads:[~2004-01-10 16:08 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-01-10 16:19 ` 2.6.0 NFS-server low to 0 performance Trond Myklebust
2004-01-12 14:40 James Pearson
2004-01-12 15:22 ` Trond Myklebust
2004-01-13 11:08 ` Muli Ben-Yehuda
-- 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=m3eku74whi.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox