From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Status of mount.nfs
Date: Tue, 24 Jul 2007 13:51:59 -0400 [thread overview]
Message-ID: <1185299519.6586.28.camel@localhost> (raw)
In-Reply-To: <20070722220442.GA32331@uio.no>
On Mon, 2007-07-23 at 00:04 +0200, Steinar H. Gunderson wrote:
> On Sun, Jul 22, 2007 at 05:58:13PM -0400, Trond Myklebust wrote:
> > The default _had_ to change to TCP because UDP is just too unreliable
> > for NFS running with large (> 8k) r/w sizes, or on nonhomogeneous
> > networks (mixed 10/100/1000Gbit), or with fast clients.
>
> Are you saying it changed between util-linux mount and nfs-utils mount.nfs? I
> thought that change happened a lot earlier, and that this was something else.
The private versions of util-linux maintained by RedHat and SuSE (and
Debian?) transitioned earlier, but I don't believe we ever sent those
patches to the upstream maintainers of util-linux.
Trond
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-07-24 17:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 19:16 Status of mount.nfs Steinar H. Gunderson
2007-07-08 23:16 ` Chuck Lever
2007-07-09 3:17 ` Neil Brown
2007-07-09 9:55 ` Steinar H. Gunderson
2007-07-09 16:45 ` Chuck Lever
2007-07-10 0:08 ` Neil Brown
2007-07-15 8:31 ` Steinar H. Gunderson
2007-07-16 1:13 ` Neil Brown
2007-07-16 9:20 ` Steinar H. Gunderson
2007-07-16 10:15 ` Neil Brown
2007-07-22 19:17 ` Steinar H. Gunderson
2007-07-22 21:58 ` Trond Myklebust
2007-07-22 22:04 ` Steinar H. Gunderson
2007-07-24 17:51 ` Trond Myklebust [this message]
[not found] ` <46A52816.6050500@oracle.com>
2007-07-24 17:24 ` Steinar H. Gunderson
2007-07-24 17:50 ` Trond Myklebust
2007-07-24 17:55 ` Steinar H. Gunderson
2007-07-24 20:46 ` Chuck Lever
2007-07-24 21:10 ` Trond Myklebust
2007-07-24 21:18 ` Chuck Lever
2007-07-25 2:08 ` rpcbind behavior on Fedora 7 Chuck Lever
2007-07-25 19:35 ` Status of mount.nfs Chuck Lever
2007-07-26 12:47 ` Steve Dickson
2007-07-27 3:02 ` Chuck Lever
2007-07-27 15:00 ` Steve Dickson
2007-07-27 15:56 ` Trond Myklebust
2007-07-27 16:16 ` Steve Dickson
2007-07-27 16:27 ` Trond Myklebust
2007-07-27 17:07 ` Steve Dickson
2007-07-27 17:13 ` Trond Myklebust
2007-07-27 21:38 ` Chuck Lever
2007-07-28 12:51 ` Steve Dickson
2007-07-31 18:30 ` Trond Myklebust
2007-07-31 21:28 ` Chuck Lever
2007-08-01 10:58 ` Steve Dickson
2007-08-01 20:02 ` Chuck Lever
2007-08-01 21:12 ` Steve Dickson
2007-08-02 16:20 ` Chuck Lever
2007-08-02 18:42 ` Trond Myklebust
2007-08-02 21:43 ` Chuck Lever
2007-08-03 13:02 ` Trond Myklebust
2007-08-02 20:46 ` Steve Dickson
2007-07-27 19:37 ` Chuck Lever
2007-07-28 13:20 ` Steve Dickson
2007-07-28 21:00 ` Chuck Lever
2007-07-29 19:24 ` Steve Dickson
2007-07-30 4:14 ` Chuck Lever
2007-07-24 23:41 ` Steinar H. Gunderson
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=1185299519.6586.28.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=sgunderson@bigfoot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox