From: Valdis.Kletnieks@vt.edu
To: lwoodman@redhat.com
Cc: Christoph Lameter <cl@linux.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Motohiro Kosaki <mkosaki@redhat.com>
Subject: Re: [PATCH -mm] do_migrate_pages() calls migrate_to_node() even if task is already on a correct node
Date: Thu, 22 Mar 2012 15:36:56 -0400 [thread overview]
Message-ID: <40300.1332445016@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 22 Mar 2012 15:07:00 -0400." <4F6B7854.1040203@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
On Thu, 22 Mar 2012 15:07:00 -0400, Larry Woodman said:
> So to be clear on this, in that case the intention would be move 3 to 4,
> 4 to 5 and 5 to 6
> to keep the node ordering the same?
Would it make more sense to do 5->6, 4->5, 3->4? If we move stuff
from 3 to 4 before clearing the old 4 stuff out, it might get crowded?
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-03-22 19:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 18:14 Larry Woodman
2012-03-22 18:22 ` Rik van Riel
2012-03-22 18:45 ` KOSAKI Motohiro
2012-03-22 18:47 ` Rik van Riel
2012-03-22 18:49 ` Larry Woodman
2012-03-22 18:51 ` Christoph Lameter
2012-03-22 19:07 ` Larry Woodman
2012-03-22 19:30 ` Christoph Lameter
2012-03-29 18:00 ` Larry Woodman
2012-03-29 19:43 ` KOSAKI Motohiro
2012-03-29 20:01 ` Larry Woodman
2012-03-30 16:15 ` Christoph Lameter
2012-03-30 17:30 ` Larry Woodman
2012-03-30 20:49 ` Christoph Lameter
2012-03-22 19:36 ` Valdis.Kletnieks [this message]
2012-03-22 19:41 ` Christoph Lameter
2012-03-22 20:14 ` Larry Woodman
2012-03-23 1:21 ` Valdis.Kletnieks
2012-03-22 19:07 ` KOSAKI Motohiro
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=40300.1332445016@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=mkosaki@redhat.com \
--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