From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
minchan.kim@gmail.com, Bob Liu <lliubbo@gmail.com>,
fujita.tomonori@lab.ntt.co.jp, m.nazarewicz@samsung.com,
pawel@osciak.com, andi.kleen@intel.com,
felipe.contreras@gmail.com,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: [PATCH 4/4] alloc_contig_pages() use better allocation function for migration
Date: Fri, 19 Nov 2010 17:16:53 +0900 [thread overview]
Message-ID: <20101119171653.3c476064.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20101119171033.a8d9dc8f.kamezawa.hiroyu@jp.fujitsu.com>
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Old story.
Because we cannot assume which memory section will be offlined next,
hotremove_migrate_alloc() just uses alloc_page(). i.e. make no decision
where the page should be migrate into. Considering memory hotplug's
nature, the next memory section near to a section which is being removed
will be removed in the next. So, migrate pages to the same node of original
page doesn't make sense in many case, it just increases load.
Migration destination page is allocated from the node where offlining script
runs.
Now, contiguous-alloc uses do_migrate_range(). In this case, migration
destination node should be the same node of migration source page.
This patch modifies hotremove_migrate_alloc() and pass "nid" to it.
Memory hotremove will pass -1. So, if the page will be moved to
the node where offlining script runs....no behavior changes.
Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
include/linux/page-isolation.h | 3 ++-
mm/memory_hotplug.c | 2 +-
mm/page_isolation.c | 21 ++++++++++++++++-----
3 files changed, 19 insertions(+), 7 deletions(-)
Index: mmotm-1117/include/linux/page-isolation.h
===================================================================
--- mmotm-1117.orig/include/linux/page-isolation.h
+++ mmotm-1117/include/linux/page-isolation.h
@@ -41,7 +41,8 @@ extern void alloc_contig_freed_pages(uns
int test_pages_in_a_zone(unsigned long start_pfn, unsigned long end_pfn);
unsigned long scan_lru_pages(unsigned long start, unsigned long end);
-int do_migrate_range(unsigned long start_pfn, unsigned long end_pfn);
+int do_migrate_range(unsigned long start_pfn,
+ unsigned long end_pfn, int node);
/*
* For large alloc.
Index: mmotm-1117/mm/memory_hotplug.c
===================================================================
--- mmotm-1117.orig/mm/memory_hotplug.c
+++ mmotm-1117/mm/memory_hotplug.c
@@ -724,7 +724,7 @@ repeat:
pfn = scan_lru_pages(start_pfn, end_pfn);
if (pfn) { /* We have page on LRU */
- ret = do_migrate_range(pfn, end_pfn);
+ ret = do_migrate_range(pfn, end_pfn, numa_node_id());
if (!ret) {
drain = 1;
goto repeat;
Index: mmotm-1117/mm/page_isolation.c
===================================================================
--- mmotm-1117.orig/mm/page_isolation.c
+++ mmotm-1117/mm/page_isolation.c
@@ -193,12 +193,21 @@ unsigned long scan_lru_pages(unsigned lo
struct page *
hotremove_migrate_alloc(struct page *page, unsigned long private, int **x)
{
- /* This should be improooooved!! */
- return alloc_page(GFP_HIGHUSER_MOVABLE);
+ return alloc_pages_node(private, GFP_HIGHUSER_MOVABLE, 0);
}
+/*
+ * Migrate pages in the range to somewhere. Migration target page is allocated
+ * by hotremove_migrate_alloc(). If on_node is specicied, new page will be
+ * selected from nearby nodes. At hotremove, this "allocate from near node"
+ * can be harmful because we may remove other pages in the node for removing
+ * more pages in node. contiguous_alloc() uses on_node=true for avoiding
+ * unnecessary migration to far node.
+ */
+
#define NR_OFFLINE_AT_ONCE_PAGES (256)
-int do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
+int do_migrate_range(unsigned long start_pfn, unsigned long end_pfn,
+ int node)
{
unsigned long pfn;
struct page *page;
@@ -245,7 +254,7 @@ int do_migrate_range(unsigned long start
goto out;
}
/* this function returns # of failed pages */
- ret = migrate_pages(&source, hotremove_migrate_alloc, 0, 1);
+ ret = migrate_pages(&source, hotremove_migrate_alloc, node, 1);
if (ret)
putback_lru_pages(&source);
}
@@ -463,6 +472,7 @@ struct page *__alloc_contig_pages(unsign
struct zonelist *zonelist;
enum zone_type highzone_idx = gfp_zone(gfpflag);
unsigned long zone_start, zone_end, rs, re, pos;
+ int target_node;
if (node == -1)
node = numa_node_id();
@@ -516,6 +526,7 @@ retry:
if (!zone)
return NULL;
+ target_node = zone->zone_pgdat->node_id;
zone_start = ALIGN(zone->zone_start_pfn, 1 << align_order);
zone_end = zone->zone_start_pfn + zone->spanned_pages;
@@ -548,7 +559,7 @@ next_zone:
for (rs = scan_lru_pages(rs, re);
rs && rs < re;
rs = scan_lru_pages(rs, re)) {
- int rc = do_migrate_range(rs, re);
+ int rc = do_migrate_range(rs, re, target_node);
if (!rc)
migration_failed = 0;
else {
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-19 8:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 8:10 [PATCH 0/4] big chunk memory allocator v4 KAMEZAWA Hiroyuki
2010-11-19 8:12 ` [PATCH 1/4] alloc_contig_pages() move some functions to page_isolation.c KAMEZAWA Hiroyuki
2010-11-21 15:07 ` Minchan Kim
2010-11-19 8:14 ` [PATCH 2/4] alloc_contig_pages() find appropriate physical memory range KAMEZAWA Hiroyuki
2010-11-21 15:21 ` Minchan Kim
2010-11-22 0:11 ` KAMEZAWA Hiroyuki
2010-11-22 11:20 ` Minchan Kim
2010-11-24 0:15 ` KAMEZAWA Hiroyuki
2010-11-19 8:15 ` [PATCH 3/4] alloc_contig_pages() allocate big chunk memory using migration KAMEZAWA Hiroyuki
2010-11-21 15:25 ` Minchan Kim
2010-11-22 0:13 ` KAMEZAWA Hiroyuki
2010-11-22 11:44 ` Minchan Kim
2010-11-24 0:20 ` KAMEZAWA Hiroyuki
2010-11-19 8:16 ` KAMEZAWA Hiroyuki [this message]
2010-11-22 12:01 ` [PATCH 4/4] alloc_contig_pages() use better allocation function for migration Minchan Kim
2010-11-19 20:56 ` [PATCH 0/4] big chunk memory allocator v4 Andrew Morton
2010-11-22 0:04 ` KAMEZAWA Hiroyuki
2010-11-23 15:46 ` Michał Nazarewicz
2010-11-24 0:36 ` KAMEZAWA Hiroyuki
2010-11-22 0:30 ` Felipe Contreras
2010-11-22 8:59 ` Kleen, Andi
2010-11-23 15:44 ` Michał Nazarewicz
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=20101119171653.3c476064.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=felipe.contreras@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=m.nazarewicz@samsung.com \
--cc=minchan.kim@gmail.com \
--cc=pawel@osciak.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