From: Christoph Lameter <cl@linux-foundation.org>
To: Bob Liu <lliubbo@gmail.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
lee.schermerhorn@hp.com, andi@firstfloor.org,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: [RFC][PATCH] migrate_pages:skip migration between intersect nodes
Date: Wed, 31 Mar 2010 09:17:30 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003310914290.17298@router.home> (raw)
In-Reply-To: <cf18f8341003301836i248d716as8d90c130790194ff@mail.gmail.com>
On Wed, 31 Mar 2010, Bob Liu wrote:
> > The intended semantic is the preservation of the relative position of the
> > page to the beginning of the node set. If you do not want to preserve the
> > relative position then just move portions of the nodes around.
> >
>
> Hmm.,
> Sorry I still haven't understand your mention :-)
>
> My concern was why move the pages in the intersect nodes.I think skipping
> this migration we can also satisfy the user's request.
> In the above semantic, I haven't got the result.
No skipping does *not* satisfy the users request since the relative
position of the page from the beginning of the nodesset is not
preserved.
You end up with a mess without this requirement. F.e. if you use page
migration (or cpuset automigration) to shift an application running on 10
nodes up by two nodes to make a hole that would allow you to run another
application on the lower nodes. Applications place pages intentionally on
certain nodes to be able to manage memory distances.
--
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>
prev parent reply other threads:[~2010-03-31 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 14:57 Bob Liu
2010-03-29 15:31 ` Lee Schermerhorn
2010-03-29 23:41 ` KOSAKI Motohiro
2010-03-30 16:28 ` Christoph Lameter
2010-03-30 16:49 ` Andi Kleen
2010-03-30 0:03 ` Minchan Kim
2010-03-30 16:29 ` Christoph Lameter
2010-03-31 1:36 ` Bob Liu
2010-03-31 3:56 ` Minchan Kim
2010-03-31 4:02 ` Bob Liu
2010-03-31 14:17 ` Christoph Lameter [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=alpine.DEB.2.00.1003310914290.17298@router.home \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=minchan.kim@gmail.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