From: Wang Nan <wangnan0@huawei.com>
To: Ingo Molnar <mingo@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
"Mel Gorman" <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Dave Hansen" <dave.hansen@intel.com>,
Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: wangnan0@huawei.com, linux-ia64@vger.kernel.org,
peifeiyue@huawei.com, linux-sh@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 2/7] memory-hotplug: x86_64: suitable memory should go to ZONE_MOVABLE
Date: Mon, 21 Jul 2014 11:46:37 +0800 [thread overview]
Message-ID: <1405914402-66212-3-git-send-email-wangnan0@huawei.com> (raw)
In-Reply-To: <1405914402-66212-1-git-send-email-wangnan0@huawei.com>
This patch introduces zone_for_memory() to arch_add_memory() on x86_64
to ensure new, higher memory added into ZONE_MOVABLE if movable zone has
already setup.
Signed-off-by: Wang Nan <wangnan0@huawei.com>
Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: Dave Hansen <dave.hansen@intel.com>
---
arch/x86/mm/init_64.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index df1a992..5621c47 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -691,7 +691,8 @@ static void update_end_of_memory_vars(u64 start, u64 size)
int arch_add_memory(int nid, u64 start, u64 size)
{
struct pglist_data *pgdat = NODE_DATA(nid);
- struct zone *zone = pgdat->node_zones + ZONE_NORMAL;
+ struct zone *zone = pgdat->node_zones +
+ zone_for_memory(nid, start, size, ZONE_NORMAL);
unsigned long start_pfn = start >> PAGE_SHIFT;
unsigned long nr_pages = size >> PAGE_SHIFT;
int ret;
--
1.8.4
next prev parent reply other threads:[~2014-07-21 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 3:46 [PATCH v2 0/7] memory-hotplug: suitable memory should go to ZONE_MOVABLE Wang Nan
2014-07-21 3:46 ` [PATCH v2 1/7] memory-hotplug: add zone_for_memory() for selecting zone for new memory Wang Nan
2014-07-21 17:19 ` Sergei Shtylyov
2014-07-21 3:46 ` Wang Nan [this message]
2014-07-21 3:46 ` [PATCH v2 3/7] memory-hotplug: x86_32: suitable memory should go to ZONE_MOVABLE Wang Nan
2014-07-21 3:46 ` [PATCH v2 4/7] memory-hotplug: ia64: " Wang Nan
2014-07-21 3:46 ` [PATCH v2 5/7] memory-hotplug: ppc: " Wang Nan
2014-07-21 3:46 ` [PATCH v2 6/7] memory-hotplug: sh: " Wang Nan
2014-07-21 3:46 ` [PATCH v2 7/7] memory-hotplug: tile: " Wang Nan
2014-07-22 3:09 ` Wang Nan
2014-07-31 20:43 ` Chris Metcalf
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=1405914402-66212-3-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peifeiyue@huawei.com \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
--cc=zhangyanfei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).