From: Christoph Lameter <clameter@sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Minor [?] page migration bug in check_pte_range()
Date: Tue, 14 Aug 2007 12:33:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708141231210.30435@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1187105148.6281.38.camel@localhost>
On Tue, 14 Aug 2007, Lee Schermerhorn wrote:
> What I see is that when you attempt to install an interleave policy and
> migrate the pages to match that policy, any pages on nodes included in
> the interleave node mask will not be migrated to match policy. This
Right. The pages are already on permitted nodes.
> occurs because of the clever, but overly simplistic test in
> check_pte_range():
>
> if (node_isset(nid, *nodes) == !!(flags & MPOL_MF_INVERT))
> continue;
>
> Fixing this would, I think, involve checking each page against the
> location dictated by the new policy. Altho' I don't think this is a
> performance critical path, it is the inner-most loop of check_range().
>
> Is this worth addressing, do you think?
This is not going to be easy because you would have to move each
individual pages to a particular node. Or setup lists for each node and
then do several calls to migrate page.
I think we can leave it as is.
--
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-08-14 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 15:25 Lee Schermerhorn
2007-08-14 19:33 ` Christoph Lameter [this message]
2007-08-14 20:21 ` Lee Schermerhorn
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.0708141231210.30435@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/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