From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Harald Hannelius <harald+nfs@arcada.fi>,
Olaf Kirch <okir@suse.de>,
nfs@lists.sourceforge.net
Subject: Re: Poor NFS performance, kernel 2.6.6.
Date: Tue, 1 Jun 2004 08:16:58 +0800 [thread overview]
Message-ID: <20040601001658.GA7373@outblaze.com> (raw)
In-Reply-To: <1085771968.3882.17.camel@lade.trondhjem.org>
> > I guess (as a total don't-know) that nfsd reads and writes files in a
> > different way than local processes do. I read somewhere something about
> > read-ahead but that was in 2.6.0-pre-something..
>
> Hmm... The current readahead code does a load of crap in order to
> determine whether or not the user is doing linear or random I/O. It may
> be that the nfsd server with all its multi-threading and out-of-sequence
> I/O is triggering the random I/O readahead code (which of course aims to
> limit readahead).
Any thoughts on this patch posted to lkml
http://marc.theaimsgroup.com/?l=linux-kernel&m=108603045809565&w=2
Regards, /yg
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-06-01 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 10:31 Poor NFS performance, kernel 2.6.6 Harald Hannelius
[not found] ` <200405271251.22746.vincent.roqueta@ext.bull.net>
2004-05-27 12:17 ` Harald Hannelius
2004-05-27 12:45 ` Vincent ROQUETA
2004-05-27 12:39 ` Dexter Filmore
2004-05-27 13:03 ` Harald Hannelius
2004-05-27 18:07 ` Bernd Schubert
2004-05-27 19:01 ` Trond Myklebust
2004-05-27 20:56 ` Harald Hannelius
2004-05-27 22:09 ` Trond Myklebust
2004-05-28 7:17 ` Harald Hannelius
2004-05-28 13:55 ` Olaf Kirch
2004-05-28 16:57 ` Phy Prabab
2004-05-28 18:03 ` Harald Hannelius
2004-05-28 19:19 ` Trond Myklebust
2004-06-01 0:16 ` Yusuf Goolamabbas [this message]
2004-06-02 6:57 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-05-27 13:16 Harald Hannelius
2004-06-02 12:33 Jeffrey Layton
2004-06-02 13:00 ` Greg Banks
2004-06-02 13:40 ` Jeffrey Layton
2004-06-02 13:14 ` Vincent ROQUETA
2004-06-02 14:53 ` Jeffrey Layton
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=20040601001658.GA7373@outblaze.com \
--to=yusufg@outblaze.com \
--cc=harald+nfs@arcada.fi \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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.