All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mel Gorman <mgorman@suse.de>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Minchan Kim <minchan@kernel.org>
Subject: [PATCH v3 0/4] memory-hotplug: handle page race between allocation and isolation
Date: Fri,  7 Sep 2012 09:39:28 +0900	[thread overview]
Message-ID: <1346978372-17903-1-git-send-email-minchan@kernel.org> (raw)

Memory hotplug has a subtle race problem so this patchset fixes the problem
(Look at [3/3] for detail and please confirm the problem before review
other patches in this series.)

 [1/4] is just clean up and help for [2/4].
 [2/4] keeps the migratetype information to freed page's index field
       and [3/4] uses the information.
 [3/4] fixes the race problem with [2/4]'s information.
 [4/4] enhance memory-hotremove operation success ratio

After applying [2/4], migratetype argument in __free_one_page
and free_one_page is redundant so we can remove it but I decide
to not touch them because it increases code size about 50 byte.

This patchset is based on mmotm-2012-09-06-16-46

Minchan Kim (4):
  use get_page_migratetype instead of page_private
  mm: remain migratetype in freed page
  memory-hotplug: bug fix race between isolation and allocation
  memory-hotplug: fix pages missed by race rather than failing

 include/linux/mm.h             |   12 ++++++++++++
 include/linux/page-isolation.h |    4 ++++
 mm/page_alloc.c                |   19 ++++++++++++-------
 mm/page_isolation.c            |   18 ++++++++++++++++--
 4 files changed, 44 insertions(+), 9 deletions(-)

-- 
1.7.9.5

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mel Gorman <mgorman@suse.de>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Minchan Kim <minchan@kernel.org>
Subject: [PATCH v3 0/4] memory-hotplug: handle page race between allocation and isolation
Date: Fri,  7 Sep 2012 09:39:28 +0900	[thread overview]
Message-ID: <1346978372-17903-1-git-send-email-minchan@kernel.org> (raw)

Memory hotplug has a subtle race problem so this patchset fixes the problem
(Look at [3/3] for detail and please confirm the problem before review
other patches in this series.)

 [1/4] is just clean up and help for [2/4].
 [2/4] keeps the migratetype information to freed page's index field
       and [3/4] uses the information.
 [3/4] fixes the race problem with [2/4]'s information.
 [4/4] enhance memory-hotremove operation success ratio

After applying [2/4], migratetype argument in __free_one_page
and free_one_page is redundant so we can remove it but I decide
to not touch them because it increases code size about 50 byte.

This patchset is based on mmotm-2012-09-06-16-46

Minchan Kim (4):
  use get_page_migratetype instead of page_private
  mm: remain migratetype in freed page
  memory-hotplug: bug fix race between isolation and allocation
  memory-hotplug: fix pages missed by race rather than failing

 include/linux/mm.h             |   12 ++++++++++++
 include/linux/page-isolation.h |    4 ++++
 mm/page_alloc.c                |   19 ++++++++++++-------
 mm/page_isolation.c            |   18 ++++++++++++++++--
 4 files changed, 44 insertions(+), 9 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2012-09-07  0:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  0:39 Minchan Kim [this message]
2012-09-07  0:39 ` [PATCH v3 0/4] memory-hotplug: handle page race between allocation and isolation Minchan Kim
2012-09-07  0:39 ` [PATCH v3 1/4] use get_freepage_migratetype instead of page_private Minchan Kim
2012-09-07  0:39   ` Minchan Kim
2012-09-07  3:50   ` Yasuaki Ishimatsu
2012-09-07  3:50     ` Yasuaki Ishimatsu
2012-09-07  0:39 ` [PATCH v3 2/4] mm: remain migratetype in freed page Minchan Kim
2012-09-07  0:39   ` Minchan Kim
2012-09-07  3:51   ` Yasuaki Ishimatsu
2012-09-07  3:51     ` Yasuaki Ishimatsu
2012-09-07  0:39 ` [PATCH v3 3/4] memory-hotplug: bug fix race between isolation and allocation Minchan Kim
2012-09-07  0:39   ` Minchan Kim
2012-09-07  3:52   ` Yasuaki Ishimatsu
2012-09-07  3:52     ` Yasuaki Ishimatsu
2012-09-07  0:39 ` [PATCH v3 4/4] memory-hotplug: fix pages missed by race rather than failng Minchan Kim
2012-09-07  0:39   ` Minchan Kim
2012-09-07  0:48   ` Kamezawa Hiroyuki
2012-09-07  0:48     ` Kamezawa Hiroyuki
2012-09-07  9:17 ` [PATCH v3 0/4] memory-hotplug: handle page race between allocation and isolation Mel Gorman
2012-09-07  9:17   ` Mel Gorman

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=1346978372-17903-1-git-send-email-minchan@kernel.org \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=qiuxishi@huawei.com \
    --cc=wency@cn.fujitsu.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 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.