From: Martin Knoblauch <knobi@knobisoft.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Greg Banks <gnb@melbourne.sgi.com>
Cc: linux-nfs list <linux-nfs@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable
Date: Thu, 18 Sep 2008 00:42:58 -0700 (PDT) [thread overview]
Message-ID: <418380.19358.qm@web32608.mail.mud.yahoo.com> (raw)
----- Original Message ----
> From: Andrew Morton <akpm@linux-foundation.org>
> To: Greg Banks <gnb@melbourne.sgi.com>
> Cc: Martin Knoblauch <knobi@knobisoft.de>; linux-nfs list <linux-nfs@vger.kernel.org>; linux-kernel@vger.kernel.org
> Sent: Thursday, September 18, 2008 5:13:34 AM
> Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable
>
> On Thu, 18 Sep 2008 11:42:54 +1000 Greg Banks wrote:
>
> > I think having a tunable for client readahead is an excellent idea,
> > although not to solve your particular problem. The SLES10 kernel has a
> > patch which does precisely that, perhaps Neil could post it.
> >
> > I don't think there's a lot of point having both a module parameter and
> > a sysctl.
>
> mount -o remount,readahead=42
[root@lpsdm52 ~]# mount -o remount,readahead=42 /net/spsdms/fs13
Bad nfs mount parameter: readahead
[root@lpsdm52 ~]# mount -o readahead=42 /net/spsdms/fs13
Bad nfs mount parameter: readahead
I assume the reply was meant to say that the correct way of introducing a modifyable readahead size is to implement it as a mount option ? :-) I considered it, but it seems to be more intrusive than the workaround patch. It also needs changes to userspace tools - correct?
Cheers
Martin
next reply other threads:[~2008-09-18 7:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 7:42 Martin Knoblauch [this message]
2008-09-18 8:18 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-09-21 12:53 Martin Knoblauch
2008-09-21 12:50 Martin Knoblauch
2008-09-21 13:53 ` Chuck Lever
2008-09-18 11:53 Martin Knoblauch
2008-09-18 18:24 ` Chuck Lever
2008-09-18 19:03 ` Peter Staubach
2008-09-18 9:32 Martin Knoblauch
2008-09-18 8:38 Martin Knoblauch
2008-09-18 8:47 ` Andrew Morton
2008-09-18 8:57 ` Greg Banks
2008-09-18 13:20 ` Peter Zijlstra
2008-09-18 8:19 Martin Knoblauch
2008-09-18 8:45 ` Greg Banks
2008-09-17 17:01 Martin Knoblauch
2008-09-17 16:23 Martin Knoblauch
2008-09-17 16:43 ` Chuck Lever
2008-09-17 16:15 Martin Knoblauch
2008-09-17 16:10 Martin Knoblauch
2008-09-17 16:03 Martin Knoblauch
2008-09-17 13:42 Michael Trimarchi
2008-09-17 13:27 Martin Knoblauch
2008-09-17 13:19 Michael Trimarchi
2008-09-17 13:06 Martin Knoblauch
2008-09-17 14:06 ` Peter Staubach
2008-09-17 15:41 ` Chuck Lever
2008-09-18 1:42 ` Greg Banks
2008-09-18 3:13 ` Andrew Morton
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=418380.19358.qm@web32608.mail.mud.yahoo.com \
--to=knobi@knobisoft.de \
--cc=akpm@linux-foundation.org \
--cc=gnb@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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
Powered by JetHome