From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, lhms-devel@lists.sourceforge.net,
Cliff Wickman <cpw@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Direct Migration V6: Overview
Date: Thu, 01 Dec 2005 08:52:19 +0900 [thread overview]
Message-ID: <438E3B33.2030807@jp.fujitsu.com> (raw)
In-Reply-To: <20051130171056.19405.95644.sendpatchset@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> Changes V5->V6:
> - Patchset against 2.6.15-rc3-mm1
> - Remove checks for page count increases while migrating after Andrew assured
Could you point where is changed in the code ?
> me that this cannot happen. Revise documentation to reflect that. If this is
> the case then we will have no need to include the unwind code from the
> hotplug project in the future.
-- Kame
next prev parent reply other threads:[~2005-11-30 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 17:10 [PATCH 0/5] Direct Migration V6: Overview Christoph Lameter
2005-11-30 17:11 ` [PATCH 1/5] Direct Migration V6: PageSwapCache checks Christoph Lameter
2005-11-30 17:11 ` [PATCH 2/5] Direct Migration V6: migrate_pages() extension Christoph Lameter
2005-11-30 17:11 ` [PATCH 3/5] Direct Migration V6: remove_from_swap() to remove swap ptes Christoph Lameter
2005-11-30 17:11 ` [PATCH 4/5] Direct Migration V6: upgrade MPOL_MF_MOVE and sys_migrate_pages() Christoph Lameter
2005-11-30 17:11 ` [PATCH 5/5] Direct Migration V6: Avoid writeback / page_migrate() method Christoph Lameter
2005-11-30 23:52 ` KAMEZAWA Hiroyuki [this message]
2005-12-01 0:05 ` [PATCH 0/5] Direct Migration V6: Overview Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-12-05 19:50 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=438E3B33.2030807@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=cpw@sgi.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.