From: Hiroyuki Kamezawa <kamezawa.hiroyuki@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Wu Fengguang <fengguang.wu@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kleen, Andi" <andi.kleen@intel.com>,
Haicheng Li <haicheng.li@linux.intel.com>,
Christoph Lameter <cl@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mel Gorman <mel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Make is_mem_section_removable more conformable with offlining code
Date: Thu, 2 Sep 2010 23:19:18 +0900 [thread overview]
Message-ID: <AANLkTikYt3Hu_XeNuwAa9KjzfWgpC8cNen6q657ZKmm-@mail.gmail.com> (raw)
In-Reply-To: <20100902131855.GC10265@tiehlicka.suse.cz>
2010/9/2 Michal Hocko <mhocko@suse.cz>:
> What about this? Just compile tested.
>
> ---
> From a2aaeafbaeb5b195b699df25060128b9e547949c Mon Sep 17 00:00:00 2001
> From: Michal Hocko <mhocko@suse.cz>
> Date: Fri, 20 Aug 2010 15:39:16 +0200
> Subject: [PATCH] Make is_mem_section_removable more conformable with offlining code
>
> Currently is_mem_section_removable checks whether each pageblock from
> the given pfn range is of MIGRATE_MOVABLE type or if it is free. If both
> are false then the range is considered non removable.
>
> On the other hand, offlining code (more specifically
> set_migratetype_isolate) doesn't care whether a page is free and instead
> it just checks the migrate type of the page and whether the page's zone
> is movable.
>
> This can lead into a situation when we can mark a node as not removable
> just because a pageblock is MIGRATE_RESERVE and it is not free but still
> movable.
>
> Let's make a common helper is_page_removable which unifies both tests
> at one place.
>
> Do not rely on any of MIGRATE_* types as all others than MIGRATE_MOVABLE
> may be tricky. MIGRATE_RESERVE can be anything that just happened to
> fallback to that allocation, MIGRATE_RECLAIMABLE can be unmovable
> because slab (or what ever) has this page currently in use. If we tried
> to remove those pages and the isolation failed then those blocks
> would get to the MIRAGTE_MOVABLE list and we will end up with the
> unmovable pages in the movable zone.
>
> Let's, instead, check just whether a pageblock contains free or LRU
> pages.
>
> Signed-off-by: Michal Hocko <mhocko@suse.cz>
> ---
> include/linux/mmzone.h | 24 ++++++++++++++++++++++++
> mm/memory_hotplug.c | 19 +------------------
> mm/page_alloc.c | 5 +----
> 3 files changed, 26 insertions(+), 22 deletions(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index 6e6e626..0bd941b 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -669,6 +669,30 @@ unsigned long __init node_memmap_size_bytes(int, unsigned long, unsigned long);
> */
> #define zone_idx(zone) ((zone) - (zone)->zone_pgdat->node_zones)
>
> +#ifdef CONFIG_MEMORY_HOTREMOVE
> +/*
> + * A free or LRU pages block are removable
> + * Do not use MIGRATE_MOVABLE because it can be insufficient and
> + * other MIGRATE types are tricky.
> + */
> +static inline bool is_page_removable(struct page *page)
> +{
> + int page_block = 1 << pageblock_order;
> + for (page_block > 0) {
for ?
> + if (PageBuddy(page)) {
> + page_block -= page_order(page);
> + }else if (PageLRU(page))
> + page_block--;
> + else
> + return false;
> + }
> +
> + return true;
> +}
Hmm. above for is intending to check all pages in the block ?
I'll look into details, tomorrow.
Thanks,
-Kame
--
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:[~2010-09-02 14:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 14:14 Michal Hocko
2010-08-22 0:42 ` Wu Fengguang
2010-08-23 9:22 ` Michal Hocko
2010-08-31 12:30 ` Michal Hocko
2010-08-31 14:19 ` Wu Fengguang
2010-08-31 14:36 ` Wu Fengguang
2010-08-31 14:59 ` Wu Fengguang
2010-09-01 1:19 ` KAMEZAWA Hiroyuki
2010-09-01 12:19 ` Michal Hocko
2010-09-01 12:41 ` Michal Hocko
2010-09-02 5:45 ` KAMEZAWA Hiroyuki
2010-09-02 8:28 ` Michal Hocko
2010-09-02 9:03 ` KAMEZAWA Hiroyuki
2010-09-02 9:24 ` Michal Hocko
2010-09-02 11:19 ` Hiroyuki Kamezawa
2010-09-02 13:18 ` Michal Hocko
2010-09-02 14:19 ` Hiroyuki Kamezawa [this message]
2010-09-02 14:39 ` Michal Hocko
2010-09-02 15:05 ` Michal Hocko
2010-09-03 3:10 ` [PATCH 0/2 v2] " KAMEZAWA Hiroyuki
2010-09-03 3:11 ` [PATCH 1/2][BUGFIX] fix next active pageblock calculation KAMEZAWA Hiroyuki
2010-09-03 3:14 ` [PATCH 2/2] Make is_mem_section_removable more conformable with offlining code KAMEZAWA Hiroyuki
2010-09-03 8:25 ` Michal Hocko
2010-09-03 9:13 ` KAMEZAWA Hiroyuki
2010-09-03 9:50 ` Michal Hocko
2010-09-03 10:05 ` KAMEZAWA Hiroyuki
2010-09-03 11:01 ` Michal Hocko
2010-09-03 11:42 ` [PATCH 2/2] Make is_mem_section_removable more conformable with offlining code v3 Michal Hocko
2010-09-04 2:55 ` Wu Fengguang
2010-09-06 9:16 ` Michal Hocko
2010-09-03 9:15 ` [PATCH 2/2] Make is_mem_section_removable more conformable with offlining code Michal Hocko
2010-09-03 9:24 ` KAMEZAWA Hiroyuki
2010-09-03 7:54 ` [PATCH 0/2 v2] " Michal Hocko
2010-09-03 7:57 ` [PATCH 3/2][BUGFIX] fix memory isolation notifier return value check KAMEZAWA Hiroyuki
2010-09-03 20:48 ` Andrew Morton
2010-09-03 22:05 ` Hiroyuki Kamezawa
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=AANLkTikYt3Hu_XeNuwAa9KjzfWgpC8cNen6q657ZKmm-@mail.gmail.com \
--to=kamezawa.hiroyuki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@linux.vnet.ibm.com \
--cc=mhocko@suse.cz \
/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