From: Peter Zijlstra <peter@programming.kicks-ass.net>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Magnus Damm <magnus@valinux.co.jp>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 00/03] Unmapped: Separate unmapped and mapped pages
Date: Sat, 11 Mar 2006 22:08:15 +0100 [thread overview]
Message-ID: <1142111295.2928.14.camel@lappy> (raw)
In-Reply-To: <aec7e5c30603100538v4942f9dbnfcc962f1a5bde190@mail.gmail.com>
On Fri, 2006-03-10 at 14:38 +0100, Magnus Damm wrote:
> On 3/10/06, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > Breaking the LRU in two like this breaks the page ordering, which makes
> > it possible for pages to stay resident even though they have much less
> > activity than pages that do get reclaimed.
>
> Yes, true. But this happens already with a per-zone LRU. LRU pages
> that happen to end up in the DMA zone will probably stay there a
> longer time than pages in the normal zone. That does not mean it is
> right to break the page ordering though, I'm just saying it happens
> already and the oldest piece of data in the global system will not be
> reclaimed first - instead there are priorities such as unmapped pages
> will be reclaimed over mapped and so on. (I strongly feel that there
> should be per-node LRU:s, but that's another story)
If reclaim works right* there is equal pressure on each zone
(proportional to their size) and hence each page will have an equal life
time expectancy.
(*) this is of course not possible for all workloads, however
balance_pgdat and the page allocator take pains to make it as true as
possible.
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peter@programming.kicks-ass.net>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Magnus Damm <magnus@valinux.co.jp>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 00/03] Unmapped: Separate unmapped and mapped pages
Date: Sat, 11 Mar 2006 22:08:15 +0100 [thread overview]
Message-ID: <1142111295.2928.14.camel@lappy> (raw)
In-Reply-To: <aec7e5c30603100538v4942f9dbnfcc962f1a5bde190@mail.gmail.com>
On Fri, 2006-03-10 at 14:38 +0100, Magnus Damm wrote:
> On 3/10/06, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > Breaking the LRU in two like this breaks the page ordering, which makes
> > it possible for pages to stay resident even though they have much less
> > activity than pages that do get reclaimed.
>
> Yes, true. But this happens already with a per-zone LRU. LRU pages
> that happen to end up in the DMA zone will probably stay there a
> longer time than pages in the normal zone. That does not mean it is
> right to break the page ordering though, I'm just saying it happens
> already and the oldest piece of data in the global system will not be
> reclaimed first - instead there are priorities such as unmapped pages
> will be reclaimed over mapped and so on. (I strongly feel that there
> should be per-node LRU:s, but that's another story)
If reclaim works right* there is equal pressure on each zone
(proportional to their size) and hence each page will have an equal life
time expectancy.
(*) this is of course not possible for all workloads, however
balance_pgdat and the page allocator take pains to make it as true as
possible.
Peter
--
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:[~2006-03-11 21:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 3:44 [PATCH 00/03] Unmapped: Separate unmapped and mapped pages Magnus Damm
2006-03-10 3:44 ` Magnus Damm
2006-03-10 3:44 ` [PATCH 01/03] Unmapped: Implement two LRU:s Magnus Damm
2006-03-10 3:44 ` Magnus Damm
2006-03-10 19:16 ` Christoph Lameter
2006-03-10 19:16 ` Christoph Lameter
2006-03-11 12:14 ` Magnus Damm
2006-03-11 12:14 ` Magnus Damm
2006-03-10 3:44 ` [PATCH 02/03] Unmapped: Modify LRU behaviour Magnus Damm
2006-03-10 3:44 ` Magnus Damm
2006-03-10 3:44 ` [PATCH 03/03] Unmapped: Add guarantee code Magnus Damm
2006-03-10 3:44 ` Magnus Damm
2006-03-10 4:57 ` Nick Piggin
2006-03-10 4:57 ` Nick Piggin
2006-03-10 6:04 ` Magnus Damm
2006-03-10 6:04 ` Magnus Damm
2006-03-10 15:41 ` Chandra Seetharaman
2006-03-10 15:41 ` Chandra Seetharaman
2006-03-11 12:29 ` Magnus Damm
2006-03-11 12:29 ` Magnus Damm
2006-03-15 15:32 ` Chandra Seetharaman
2006-03-15 15:32 ` Chandra Seetharaman
2006-03-10 4:55 ` [PATCH 00/03] Unmapped: Separate unmapped and mapped pages Nick Piggin
2006-03-10 4:55 ` Nick Piggin
2006-03-10 5:55 ` Magnus Damm
2006-03-10 5:55 ` Magnus Damm
2006-03-10 7:52 ` Arjan van de Ven
2006-03-10 7:52 ` Arjan van de Ven
2006-03-10 13:19 ` Magnus Damm
2006-03-10 13:19 ` Magnus Damm
2006-03-10 14:05 ` Arjan van de Ven
2006-03-10 14:05 ` Arjan van de Ven
2006-03-11 11:52 ` Magnus Damm
2006-03-11 11:52 ` Magnus Damm
2006-03-11 20:58 ` Peter Zijlstra
2006-03-11 20:58 ` Peter Zijlstra
2006-03-13 2:28 ` Magnus Damm
2006-03-13 2:28 ` Magnus Damm
2006-03-10 12:22 ` Peter Zijlstra
2006-03-10 12:22 ` Peter Zijlstra
2006-03-10 13:38 ` Magnus Damm
2006-03-10 13:38 ` Magnus Damm
2006-03-11 21:08 ` Peter Zijlstra [this message]
2006-03-11 21:08 ` Peter Zijlstra
2006-03-13 3:05 ` Magnus Damm
2006-03-13 3:05 ` Magnus Damm
2006-03-10 19:12 ` Christoph Lameter
2006-03-10 19:12 ` Christoph Lameter
2006-03-11 11:56 ` Magnus Damm
2006-03-11 11:56 ` Magnus Damm
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=1142111295.2928.14.camel@lappy \
--to=peter@programming.kicks-ass.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@gmail.com \
--cc=magnus@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.