linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, mel@csn.ul.ie,
	tangchen@cn.fujitsu.com, laijs@cn.fujitsu.com,
	wency@cn.fujitsu.com, mingo@elte.hu, penberg@kernel.org
Cc: torvalds@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/2] memory-hotplug: Add help info for CONFIG_MOVABLE_NODE option
Date: Mon, 17 Dec 2012 09:41:27 +0800	[thread overview]
Message-ID: <1355708488-2913-2-git-send-email-tangchen@cn.fujitsu.com> (raw)
In-Reply-To: <1355708488-2913-1-git-send-email-tangchen@cn.fujitsu.com>

This patch adds help info for CONFIG_MOVABLE_NODE option.

This option allows user to online all memory of a node as movable
memory. So that the whole node can be hotpluged. Users who don't
use hotplug feature are also fine with this option on since they
won't online memory as movable.

Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Acked-by: Ingo Molnar <mingo@kernel.org>
---
 mm/Kconfig |   10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/mm/Kconfig b/mm/Kconfig
index 71259e0..4913333 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -150,6 +150,16 @@ config MOVABLE_NODE
 	depends on X86_64
 	depends on NUMA
 	depends on BROKEN
+	help
+	  Allow a node to have only movable memory. Pages used by the kernel,
+	  such as direct mapping pages can not be migrated. So the corresponding
+	  memory device can not be hotplugged. This option allows users to online
+	  all the memory of a node as movable memory so that the whole node can
+	  be hot-unplugged. Users who don't use the hotplug feature are fine
+	  with this option on since they don't online memory as movable.
+
+	  Say Y here if you want to hotplug a whole node.
+	  Say N here if you want kernel to use memory on all nodes evenly.
 
 # eventually, we can have this option just 'select SPARSEMEM'
 config MEMORY_HOTPLUG
-- 
1.7.10.1


  reply	other threads:[~2012-12-17  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  1:41 [PATCH v2 0/2] Add help info for CONFIG_MOVABLE_NODE and disable is by default Tang Chen
2012-12-17  1:41 ` Tang Chen [this message]
2012-12-17  1:41 ` [PATCH v2 2/2] memory-hotplug: Disable CONFIG_MOVABLE_NODE option " Tang Chen
2012-12-17 11:19   ` David Rientjes

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=1355708488-2913-2-git-send-email-tangchen@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wency@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).