mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lee.Schermerhorn@hp.com,
	kosaki.motohiro@jp.fujitsu.com, lwoodman@redhat.com
Subject: Re: [PATCH][RFC] evict streaming IO cache first
Date: Tue, 15 Jul 2008 17:52:52 -0400	[thread overview]
Message-ID: <20080715175252.69072c09@cuia.bos.redhat.com> (raw)
In-Reply-To: <20080715134848.cf2204b9.akpm@linux-foundation.org>

On Tue, 15 Jul 2008 13:48:48 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 15 Jul 2008 16:09:48 -0400
> Rik van Riel <riel@redhat.com> wrote:
> 
> > This patch still needs some testing under various workloads
> > on different hardware - the approach should work but the
> > threshold may need tweaking.
> 
> More than "some"!

Agreed.  In my initial testing this patch seems to bring the
behaviour of the kernel closer to the behaviour the old VM
had, but it certainly needs lots and lots of testing!

> > When there is a lot of streaming IO going on, we do not want
> > to scan or evict pages from the working set.  The old VM used
> > to skip any mapped page, but still evict indirect blocks and
> > other data that is useful to cache.
> 
> I'd be surprised if indirect blocks are getting kicked - they tend to
> be awfully sticky due to frequent touch_buffer()s or equivalent.

If you rewrite a large enough file, they get kicked.  This
has become noticable some time between 2.6.9 and 2.6.18, but
I don't think we can point to any particular changeset that
caused it - and even if we do, chances are it does more good
than harm :)

-- 
All Rights Reversed

      reply	other threads:[~2008-07-15 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 20:09 Rik van Riel
2008-07-15 20:48 ` Andrew Morton
2008-07-15 21:52   ` Rik van Riel [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=20080715175252.69072c09@cuia.bos.redhat.com \
    --to=riel@redhat.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@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

all inboxes | Powered by JetHome®