From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brady Montz <bradym@balestra.org>, linux-kernel@vger.kernel.org
Subject: Re: mount and 2.2.18
Date: Mon, 18 Dec 2000 17:47:28 +0100 [thread overview]
Message-ID: <20001218174728.A19845@athlon.random> (raw)
In-Reply-To: <t83dfl3e65.fsf@beaker.balestra.org> <E14837m-0005lq-00@the-village.bc.nu>
In-Reply-To: <E14837m-0005lq-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Dec 18, 2000 at 04:26:52PM +0000
On Mon, Dec 18, 2000 at 04:26:52PM +0000, Alan Cox wrote:
> > Thomas Pornin <Thomas.Pornin@ens.fr> writes:
> >
> > > But NFSv3 is great; if your server is NFSv3 aware, I suggest you shift
> > > your client to NFSv3 as well. It rocks.
> >
> > Can anyone point me to some docs describing the benefits of NFSv3? Thanks.
>
> Not off hand but I can give you a very brief summary of the big one - write
> speed. NFSv2 does synchronous writes with a minimal amount of write ahead.
> NFSv3 gathers writes on the server and schedules them as the server wishes.
> The client sends write requests but before it can assume them completed
> and thus clear that part of its cache has to commit them. Normally the commit
> is done well after the I/O hit server disks, if not it waits
BTW, another relevant feature is that with 2.4.x and 2.2.18aa2 you also get >2G
files with NFSv3 (like on top of ext2).
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-18 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 22:58 mount and 2.2.18 Igor Mozetic
2000-12-18 8:42 ` Thomas Pornin
2000-12-18 16:08 ` Brady Montz
2000-12-18 16:26 ` Alan Cox
2000-12-18 16:47 ` Andrea Arcangeli [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=20001218174728.A19845@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bradym@balestra.org \
--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