From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: German San Agustin <chamocarrot@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6 NFS client read-ahead
Date: Wed, 24 May 2006 12:21:45 -0400 [thread overview]
Message-ID: <1148487705.5872.34.camel@lade.trondhjem.org> (raw)
In-Reply-To: <2bc0baf20605240453l89e5cd7w949377ead93e8b66@mail.gmail.com>
On Wed, 2006-05-24 at 13:53 +0200, German San Agustin wrote:
> We have several linux 2.6.9 accesing to a netapp filer via nfs to
> update several thousands of files. The application only need to read a
> few blocks of the files when updating so we found out that disabling
> the read-ahead on the server improve greatly the performance by
> maintaining a clean cache and decreasing the number of access to disk.
> We have been trying to disable the read-ahead in the client as well to
> reduce the access to the server even further; but we couldn't find
> where to do this in the 2.6 kernel family. Is it possible?, or it is
> simply that on 2.6 kernels it is not possible to tune the nfs client.
It is not possible, and in this case, it really shouldn't make much
difference to you either as the readahead code is adaptive: it should
automatically detect that you are doing short reads.
If you want to check that it is working, I suggest using tcpdump to
monitor the NFS traffic to that file, then comparing with a "strace"
dump.
Cheers,
Trond
prev parent reply other threads:[~2006-05-24 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2bc0baf20605240446h197b3d2fxc797404aa0e733ba@mail.gmail.com>
2006-05-24 11:53 ` German San Agustin
2006-05-24 16:21 ` Trond Myklebust [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=1148487705.5872.34.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=chamocarrot@gmail.com \
--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®