From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Shaohua Li <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] some page can't be migrated
Date: Thu, 24 Jan 2008 19:09:25 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801241908370.31942@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200801251403.23236.nickpiggin@yahoo.com.au>
On Fri, 25 Jan 2008, Nick Piggin wrote:
> On Wednesday 23 January 2008 17:22, Shaohua Li wrote:
> > Anonymous page might have fs-private metadata, the page is truncated. As
> > the page hasn't mapping, page migration refuse to migrate the page. It
> > appears the page is only freed in page reclaim and if zone watermark is
> > low, the page is never freed, as a result migration always fail. I
> > thought we could free the metadata so such page can be freed in
> > migration and make migration more reliable?
>
> Anonymous pages should not have fs-private metadata.
>
> Orphaned pages I guess you mean? They should not be accessable via
> the pagecache or the page tables, so how do they keep tangling up
> migration? Where/how is migration finding these pages?!
Is this maybe related to memory unplug or some such project?
next prev parent reply other threads:[~2008-01-25 3:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 6:22 Shaohua Li
2008-01-25 3:03 ` Nick Piggin
2008-01-25 3:09 ` Christoph Lameter [this message]
2008-01-25 3:09 ` Shaohua Li
2008-01-25 3:12 ` Christoph Lameter
2008-01-25 3:18 ` Shaohua Li
2008-01-25 5:20 ` Nick Piggin
2008-01-25 3:37 ` Christoph Lameter
2008-01-25 3:59 ` Shaohua Li
2008-01-25 4:01 ` Christoph Lameter
2008-01-25 4:17 ` Nick Piggin
2008-01-25 4:42 ` Christoph Lameter
2008-01-25 6:03 ` Shaohua Li
2008-01-27 6:03 ` Andrew Morton
2008-01-28 1:43 ` Nick Piggin
2008-01-28 1:48 ` Shaohua Li
2008-01-28 19:09 ` Christoph Lameter
2008-01-28 23:17 ` Christoph Lameter
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=Pine.LNX.4.64.0801241908370.31942@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=shaohua.li@intel.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®