From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bernd Eckenfels <ecki-news2005-01@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux NFS vs NetApp
Date: Tue, 11 Jan 2005 19:41:24 -0500 [thread overview]
Message-ID: <1105490484.15912.51.camel@lade.trondhjem.org> (raw)
In-Reply-To: <E1CoVZ2-0006f7-00@calista.eckenfels.6bone.ka-ip.net>
on den 12.01.2005 Klokka 00:36 (+0100) skreiv Bernd Eckenfels:
> However since also the read performance of Linux NFS is bad (at least not
> very well selftuning) the Hardware is not really the reason for the fast NFS
> implementation.
Indeed: NFS readahead requests are often processed out of order by the
server (due to the basic unordered nature of RPC calls, the lack of
ordering between nfsd server threads, use of UDP, etc) and so I suspect
the generic readahead algorithm will tend to default to the random
access mode in many cases where it should really be doing sequential
access.
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2005-01-12 0:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <message from Phy Prabab on Monday January 10>
2005-01-11 2:54 ` Phy Prabab
2005-01-11 3:58 ` Anton Blanchard
2005-01-11 7:42 ` Joel Jaeggli
2005-01-11 9:19 ` Valdis.Kletnieks
2005-01-11 10:01 ` Jakob Oestergaard
2005-01-11 14:43 ` J. Bruce Fields
2005-01-12 11:32 ` Jakob Oestergaard
2005-01-11 18:55 ` Valdis.Kletnieks
2005-01-11 9:54 ` Neil Brown
2005-01-11 11:38 ` Lincoln Dale
2005-01-11 22:02 ` Neil Brown
2005-01-11 23:36 ` Bernd Eckenfels
2005-01-12 0:41 ` Trond Myklebust [this message]
[not found] <200501111711.50218.as@cohaesio.com>
2005-01-11 16:21 ` J. Bruce Fields
2005-01-11 17:53 ` Anders Saaby
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=1105490484.15912.51.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=ecki-news2005-01@lina.inka.de \
--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®