From: Tang Chen <tangchen@cn.fujitsu.com>
To: rob@landley.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, yinghai@kernel.org, akpm@linux-foundation.org,
wency@cn.fujitsu.com, trenn@suse.de, liwanp@linux.vnet.ibm.com,
mgorman@suse.de, walken@google.com, riel@redhat.com,
khlebnikov@openvz.org, tj@kernel.org, minchan@kernel.org,
m.szyprowski@samsung.com, mina86@mina86.com,
laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
linfeng@cn.fujitsu.com, jiang.liu@huawei.com,
kosaki.motohiro@jp.fujitsu.com, guz.fnst@cn.fujitsu.com
Cc: x86@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RESEND PATCH part1 5/9] x86, mm, numa, acpi: Extend movablemem_map to the end of each node.
Date: Thu, 21 Mar 2013 17:20:51 +0800 [thread overview]
Message-ID: <1363857655-30658-6-git-send-email-tangchen@cn.fujitsu.com> (raw)
In-Reply-To: <1363857655-30658-1-git-send-email-tangchen@cn.fujitsu.com>
When implementing movablemem_map boot option, we introduced an array
movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
the whole node memory range, we need to extend it to the node end so that
we can use it to prevent memblock from allocating memory in the ranges
user didn't specify.
We now implement movablemem_map boot option like this:
/*
* For movablemem_map=nn[KMG]@ss[KMG]:
*
* SRAT: |_____| |_____| |_________| |_________| ......
* node id: 0 1 1 2
* user specified: |__| |___|
* movablemem_map: |___| |_________| |______| ......
*
* Using movablemem_map, we can prevent memblock from allocating memory
* on ZONE_MOVABLE at boot time.
*
* NOTE: In this case, SRAT info will be ingored.
*/
Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
---
arch/x86/mm/srat.c | 34 ++++++++++++++++++++++++++++++----
1 files changed, 30 insertions(+), 4 deletions(-)
diff --git a/arch/x86/mm/srat.c b/arch/x86/mm/srat.c
index 6cd4d33..44a9b9b 100644
--- a/arch/x86/mm/srat.c
+++ b/arch/x86/mm/srat.c
@@ -150,16 +150,42 @@ static void __init sanitize_movablemem_map(int nid, u64 start, u64 end)
start_pfn = PFN_DOWN(start);
end_pfn = PFN_UP(end);
+ /*
+ * For movablemem_map=nn[KMG]@ss[KMG]:
+ *
+ * SRAT: |_____| |_____| |_________| |_________| ......
+ * node id: 0 1 1 2
+ * user specified: |__| |___|
+ * movablemem_map: |___| |_________| |______| ......
+ *
+ * Using movablemem_map, we can prevent memblock from allocating memory
+ * on ZONE_MOVABLE at boot time.
+ */
overlap = movablemem_map_overlap(start_pfn, end_pfn);
if (overlap >= 0) {
+ /*
+ * If this range overlaps with movablemem_map, then update
+ * zone_movable_limit[nid] if it has lower start pfn.
+ */
start_pfn = max(start_pfn,
movablemem_map.map[overlap].start_pfn);
- if (zone_movable_limit[nid])
- zone_movable_limit[nid] = min(zone_movable_limit[nid],
- start_pfn);
- else
+ if (!zone_movable_limit[nid] ||
+ zone_movable_limit[nid] > start_pfn)
zone_movable_limit[nid] = start_pfn;
+
+ /* Insert the higher part of the overlapped range. */
+ if (movablemem_map.map[overlap].end_pfn < end_pfn)
+ insert_movablemem_map(start_pfn, end_pfn);
+ } else {
+ /*
+ * If this is a range higher than zone_movable_limit[nid],
+ * insert it to movablemem_map because all ranges higher than
+ * zone_movable_limit[nid] on this node will be ZONE_MOVABLE.
+ */
+ if (zone_movable_limit[nid] &&
+ start_pfn > zone_movable_limit[nid])
+ insert_movablemem_map(start_pfn, end_pfn);
}
}
#else /* CONFIG_HAVE_MEMBLOCK_NODE_MAP */
--
1.7.1
--
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:[~2013-03-21 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 9:20 [RESEND PATCH part1 0/9] Introduce movablemem_map boot option Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 1/9] x86: get pg_data_t's memory from other node Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 2/9] acpi: Print hotplug info in SRAT Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 3/9] x86, mm, numa, acpi: Add movable_memmap boot option Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 4/9] x86, mm, numa, acpi: Introduce zone_movable_limit[] to store start pfn of ZONE_MOVABLE Tang Chen
2013-03-21 9:20 ` Tang Chen [this message]
2013-03-21 9:20 ` [RESEND PATCH part1 6/9] x86, mm, numa, acpi: Support getting hotplug info from SRAT Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 7/9] x86, mm, numa, acpi: Sanitize zone_movable_limit[] Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 8/9] x86, mm, numa, acpi: make movablemem_map have higher priority Tang Chen
2013-03-21 9:20 ` [RESEND PATCH part1 9/9] x86, mm, numa, acpi: Memblock limit with movablemem_map Tang Chen
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=1363857655-30658-6-git-send-email-tangchen@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=khlebnikov@openvz.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linfeng@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@suse.de \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=trenn@suse.de \
--cc=walken@google.com \
--cc=wency@cn.fujitsu.com \
--cc=x86@kernel.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox