Linux NFS development
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi-Ys4E+72pFW0hFhg+JK9F0w@public.gmane.org>
To: Peter Staubach <staubach@redhat.com>, Chuck Lever <chucklever@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Greg Banks
	<gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>,
	linux-nfs list <linux-nfs@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Peter zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable
Date: Sun, 21 Sep 2008 05:53:32 -0700 (PDT)	[thread overview]
Message-ID: <614333.44648.qm@web32604.mail.mud.yahoo.com> (raw)



> >
> > I agree that a mount option would allow more fine-grained control over
> > readahead.  A system wide parameter controlling readahead has always
> > been a weakness.  Readahead, as implemented in the VFS, has a
> > *per-file descriptor* context, however, which operates automatically
> > (and can be tuned at run-time by an application with [mf]advise(2).
> >
> > As a future feature, this might work in better combination with the
> > per-mount bdi changes proposed by Peter to provide maximal flexibility
> > without exposing yet another confusing knob that could help some
> > workloads but hurt others.
> 
> And perhaps add some dynamic tuning capabilities to the NFS client
> code to just make it do "the right thing".  This would be better
> than any tunables and would help to serve in other situations, such
> as high bandwidth/latency networks, overloaded servers who don't
> need more read-ahead READ requests piled on, etc...
> 

 this goes over my capabilities, but would certainly help the situation. But then I would hate to see Sun/Linux going off the hook, because Linux just played nice :-)

Cheers
Martin


             reply	other threads:[~2008-09-21 12:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 12:53 Martin Knoblauch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-21 12:50 [RFC][Resend] Make NFS-Client readahead tunable Martin Knoblauch
     [not found] ` <968192.84087.qm-f6uctMgKLEavuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-21 13:53   ` Chuck Lever
2008-09-18 11:53 Martin Knoblauch
     [not found] ` <688309.69831.qm-lSXk2nNw7cevuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-18 18:24   ` Chuck Lever
     [not found]     ` <76bd70e30809181124t78c0d574gaed5702095c02921-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-18 19:03       ` Peter Staubach
2008-09-18  9:32 Martin Knoblauch
2008-09-18  8:38 Martin Knoblauch
     [not found] ` <124712.40022.qm-n7KXdZBPtPqvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
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
     [not found] ` <136998.55258.qm-RqHyxEpxwZuvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-18  8:45   ` Greg Banks
2008-09-18  7:42 Martin Knoblauch
     [not found] ` <418380.19358.qm-1+WuAixcP4WvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-18  8:18   ` Andrew Morton
2008-09-17 17:01 Martin Knoblauch
2008-09-17 16:23 Martin Knoblauch
     [not found] ` <804604.40886.qm-f6uctMgKLEavuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
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:25 Martin Knoblauch
     [not found] ` <995475.95604.qm-f6uctMgKLEavuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-17 15:31   ` Jim Rees
2008-09-17 13:19 Michael Trimarchi
2008-09-17 13:06 Martin Knoblauch
     [not found] ` <997439.5560.qm-VAEUvbQToQWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-09-17 13:21   ` Jim Rees
2008-09-17 14:06   ` Peter Staubach
2008-09-17 15:41     ` Chuck Lever
2008-09-18  1:42   ` Greg Banks
     [not found]     ` <48D1B21E.3060509-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
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=614333.44648.qm@web32604.mail.mud.yahoo.com \
    --to=knobi-ys4e+72pfw0hfhg+jk9f0w@public.gmane.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=chucklever@gmail.com \
    --cc=gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=staubach@redhat.com \
    /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