From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: Olof Johansson <olof@austin.ibm.com>, <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] SVC sockets don't disable Nagle
Date: 30 Apr 2003 14:45:19 +0200 [thread overview]
Message-ID: <shsznm8duhs.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0304301356400.15733-100000@kenzo.iwr.uni-heidelberg.de>
>>>>> " " == Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de> writes:
>> In essence, this will result in some additional network
>> overhead due to headers, but the response times will be
>> perceived as faster even for slower networks.
> True, until the network becomes too slow, then you see "server
> not responding" messages...
Anybody trying to run multi-user NFS over a 9.6Kbaud link needs their
head examined.
For *real use* situations, the total number of on-the-wire NFS
requests is currently limited to 16. In addition, TCP timeouts are
supposed to be > 1 minute. The above scenario simply will not happen.
For any reasonable setup over a slow network, the aggregation will
happen naturally anyway since the NFS layer both can and will fill the
buffers as soon as they start to empty (provided we have pending
datagrams).
For fast networks, we should at least ensure that single datagrams are
aggregated properly. The way to do that is to use MSG_MORE...
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-30 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 22:03 [PATCH] SVC sockets don't disable Nagle Olof Johansson
2003-04-29 22:42 ` Bogdan Costescu
2003-04-30 0:07 ` Olof Johansson
2003-04-30 12:06 ` Bogdan Costescu
2003-04-30 12:45 ` Trond Myklebust [this message]
2003-04-30 14:58 ` Olof Johansson
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=shsznm8duhs.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=nfs@lists.sourceforge.net \
--cc=olof@austin.ibm.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 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.