From: Lee Revell <rlrevell@joe-job.com>
To: Neil Brown <neilb@suse.de>
Cc: Bret Towe <magnade@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs udp 1000/100baseT issue
Date: Thu, 16 Mar 2006 23:13:54 -0500 [thread overview]
Message-ID: <1142568835.25258.16.camel@mindpipe> (raw)
In-Reply-To: <17434.12285.88843.708858@cse.unsw.edu.au>
On Fri, 2006-03-17 at 14:41 +1100, Neil Brown wrote:
>
> > >
> > > - use tcp
> >
> > im wondering why this isnt the default to begin with
>
> Because it wasn't that many years ago that Linux NFS didn't support
> tcp at all.
> Some distributions modify 'mount' to get it to prefer tcp over udp.
Also historical reasons that predate Linux, the original NFS
implementations were UDP only. TCP was not an option until NFSv3.
Lee
next prev parent reply other threads:[~2006-03-17 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 22:24 nfs udp 1000/100baseT issue 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 [this message]
2006-03-17 9:13 ` Helge Hafting
2006-03-17 11:18 ` Andrew Morton
2006-03-17 15:53 ` Trond Myklebust
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=1142568835.25258.16.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=neilb@suse.de \
/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