From: David Rientjes <rientjes@google.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jiang Liu <jiang.liu@huawei.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
Yinghai Lu <yinghai@kernel.org>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>
Subject: Re: [PART3 Patch 00/14] introduce N_MEMORY
Date: Wed, 31 Oct 2012 11:16:35 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1210311112010.8809@chino.kir.corp.google.com> (raw)
In-Reply-To: <1351670652-9932-1-git-send-email-wency@cn.fujitsu.com>
On Wed, 31 Oct 2012, Wen Congyang wrote:
> From: Lai Jiangshan <laijs@cn.fujitsu.com>
>
> This patch is part3 of the following patchset:
> https://lkml.org/lkml/2012/10/29/319
>
> Part1 is here:
> https://lkml.org/lkml/2012/10/31/30
>
> Part2 is here:
> http://marc.info/?l=linux-kernel&m=135166705909544&w=2
>
> You can apply this patchset without the other parts.
>
> we need a node which only contains movable memory. This feature is very
> important for node hotplug. So we will add a new nodemask
> for all memory. N_MEMORY contains movable memory but N_HIGH_MEMORY
> doesn't contain it.
>
> We don't remove N_HIGH_MEMORY because it can be used to search which
> nodes contains memory that the kernel can use.
>
This doesn't describe why we need the new node state, unfortunately. It
makes sense to boot with node(s) containing only ZONE_MOVABLE, but it
doesn't show why we need a nodemask to specify such nodes and such
information should be available from the kernel log or /proc/zoneinfo.
Node hotplug should fail if all memory cannot be offlined, so why do we
need another nodemask? Only offline the node if all memory is offlined.
--
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:[~2012-10-31 18:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 8:03 Wen Congyang
2012-10-31 8:03 ` [PART3 Patch 01/14] node_states: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 02/14] cpuset: use N_MEMORY instead N_HIGH_MEMORY Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 03/14] procfs: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 04/14] memcontrol: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 05/14] oom: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 06/14] mm,migrate: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 07/14] mempolicy: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 08/14] hugetlb: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 09/14] vmstat: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 10/14] kthread: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 11/14] init: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 12/14] vmscan: " Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 13/14] page_alloc: use N_MEMORY instead N_HIGH_MEMORY change the node_states initialization Wen Congyang
2012-10-31 8:04 ` [PART3 Patch 14/14] hotplug: update nodemasks management Wen Congyang
2012-10-31 18:16 ` David Rientjes [this message]
2012-11-01 6:13 ` [PART3 Patch 00/14] introduce N_MEMORY Wen Congyang
2012-11-01 21:36 ` David Rientjes
2012-11-02 7:41 ` Wen Congyang
2012-11-14 19:52 ` Andrew Morton
2012-11-15 6:33 ` Wen Congyang
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=alpine.DEB.2.00.1210311112010.8809@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=wency@cn.fujitsu.com \
--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