From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Kenneth Aafløy" <keaafloy@online.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange NFS behavior (?)
Date: Sun, 16 May 2004 20:51:21 -0400 [thread overview]
Message-ID: <1084755081.3770.5.camel@lade.trondhjem.org> (raw)
In-Reply-To: <200405170243.18245.keaafloy@online.no>
På su , 16/05/2004 klokka 20:43, skreiv Kenneth Aafløy:
> Why does not the NFS code (server or client) try to either limit or increase
> the buffer size when performance is at least 10x slower than that of the
> medium it's mounted on, and no other load is present?
Which buffers? We already do automatic congestion control in the RPC
layer (and in the socket layer)...
> And why is the
> performance really so bad with higher r/wsize?
Read the fine FAQ & HOWTO... The keywords are "UDP" and "fragmentation".
http://nfs.sourceforge.net
Then go, use the "tcp" mount option and be happy...
Cheers,
Trond
prev parent reply other threads:[~2004-05-17 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 0:43 Kenneth Aafløy
2004-05-17 0:51 ` 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=1084755081.3770.5.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=keaafloy@online.no \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®