From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-mm@kvack.org, mbligh@mbligh.org, riel@redhat.com
Subject: Re: [patch 1/1] vmscan: give referenced, active and unmapped pages a second trip around the LRU
Date: Fri, 25 May 2007 01:43:01 -0700 [thread overview]
Message-ID: <20070525014301.ed817a91.akpm@linux-foundation.org> (raw)
In-Reply-To: <1180082124.7348.55.camel@twins>
On Fri, 25 May 2007 10:35:24 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, 2007-05-25 at 01:01 -0700, Andrew Morton wrote:
> > On Fri, 25 May 2007 09:51:19 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > > Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> >
> > But why? It might make the VM suck. Or swap more. Or go oom.
> >
> > I don't know how to justify merging this.
>
> /me a tad confused here - what patch are we discussing?
> The ACK was for your initial patch.
Yup, that patch.
> As for my patch - yes I understand that that would be difficult, but
> sometimes you seem to just toss things in to see how they work out (one
> can always hope, right :-)
>
> As for the rationale: not clearing the referenced state when we do give
> the page another go on the active list, means it will get yet another
> one when we finally do check it (and reclaim_mapped is deemed ok).
>
> Not doing it basically gives all those pages another go after
> reclaim_mapped is set.
>
> I realise this is not backed up by evidence of actual tests,.. :-(
Well yeah. I look at this patch and I can say with confidence that it will
increase our tendency to swap and that it'll cause reclaim to scan more
pages and that it'll increase the ease with which we declare oom.
otoh it takes us closer to the designed 4-stage page aging. But does it
actually make the kernel better? Unknown and unknowable.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-05-25 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 23:57 akpm, Andrew Morton
2007-05-25 7:02 ` Peter Zijlstra
2007-05-25 7:18 ` Andrew Morton
2007-05-25 7:23 ` Peter Zijlstra
2007-05-25 7:28 ` Andrew Morton
2007-05-25 7:36 ` Peter Zijlstra
2007-05-25 7:48 ` Andrew Morton
2007-05-25 7:51 ` Peter Zijlstra
2007-05-25 8:01 ` Andrew Morton
2007-05-25 8:35 ` Peter Zijlstra
2007-05-25 8:43 ` Andrew Morton [this message]
2007-05-25 10:13 ` Peter Zijlstra
2007-05-25 14:50 ` Rik van Riel
2007-05-25 14:43 ` Rik van Riel
2007-05-25 17:20 ` 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=20070525014301.ed817a91.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=peterz@infradead.org \
--cc=riel@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