From: Ingo Molnar <mingo@kernel.org>
To: Zhang Yanfei <zhangyanfei.yes@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, "Rafael J . Wysocki" <rjw@sisk.pl>,
lenb@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
mingo@elte.hu, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Toshi Kani <toshi.kani@hp.com>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>,
Thomas Renninger <trenn@suse.de>, Yinghai Lu <yinghai@kernel.org>,
Jiang Liu <jiang.liu@huawei.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
Mel Gorman <mgorman@suse.de>, Minchan Kim <minchan@kernel.org>,
mina86@mina86.com, gong.chen@linux.intel.com,
vasilis.liaskovitis@profitbricks.com, lwoodman@redhat.com,
Rik van Riel <riel@redhat.com>,
jweiner@redhat.com, prarit@redhat.com,
"x86@kernel.org" <x86@kernel.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
linux-acpi@vger.kernel.org, imtangchen@gmail.com,
Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Subject: Re: [PATCH v5 6/6] mem-hotplug: Introduce movablenode boot option
Date: Fri, 27 Sep 2013 08:26:33 +0200 [thread overview]
Message-ID: <20130927062633.GB6726@gmail.com> (raw)
In-Reply-To: <52446413.50504@gmail.com>
* Zhang Yanfei <zhangyanfei.yes@gmail.com> wrote:
> OK. Trying below:
>
> movablenode [KNL,X86] This option enables the kernel to arrange
> hotpluggable memory into ZONE_MOVABLE zone. If memory
> in a node is all hotpluggable, the option may make
> the whole node has only one ZONE_MOVABLE zone, so that
> the whole node can be hot-removed after system is up.
> Note that this option may cause NUMA performance down.
That paragraph doesn't really parse in several places ...
Also, more importantly, please explain why this needs to be a boot option.
In terms of user friendliness boot options are at the bottom of the list,
and boot options also don't really help feature tests.
Presumably the feature is safe and has no costs, and hence could be added
as a regular .config option, with a boot option only as an additional
configurability option?
Thanks,
Ingo
--
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-09-27 6:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 18:23 [PATCH v5 0/6] x86, memblock: Allocate memory near kernel image before SRAT parsed Zhang Yanfei
2013-09-24 18:25 ` [PATCH v5 1/6] memblock: Factor out of top-down allocation Zhang Yanfei
2013-09-27 22:23 ` Toshi Kani
2013-09-24 18:27 ` [PATCH v5 2/6] memblock: Introduce bottom-up allocation mode Zhang Yanfei
2013-09-26 14:45 ` Tejun Heo
2013-09-26 15:37 ` Zhang Yanfei
2013-09-26 15:50 ` Tejun Heo
2013-09-26 15:54 ` Zhang Yanfei
2013-09-26 16:51 ` Zhang Yanfei
2013-09-27 22:29 ` Toshi Kani
2013-09-24 18:29 ` [PATCH v5 3/6] x86/mm: Factor out of top-down direct mapping setup Zhang Yanfei
2013-09-26 14:46 ` Tejun Heo
2013-09-26 15:39 ` Zhang Yanfei
2013-09-26 16:56 ` Zhang Yanfei
2013-09-27 22:43 ` Toshi Kani
2013-09-24 18:30 ` [PATCH v5 4/6] x86/mem-hotplug: Support initialize page tables in bottom-up Zhang Yanfei
2013-09-26 14:48 ` Tejun Heo
2013-09-26 15:43 ` Zhang Yanfei
2013-09-26 15:48 ` Tejun Heo
2013-09-26 16:03 ` Zhang Yanfei
2013-09-26 16:08 ` Tejun Heo
2013-09-26 17:00 ` Zhang Yanfei
2013-09-26 22:52 ` Andrew Morton
2013-09-26 22:57 ` H. Peter Anvin
2013-09-24 18:34 ` [PATCH v5 5/6] x86, acpi, crash, kdump: Do reserve_crashkernel() after SRAT is parsed Zhang Yanfei
2013-09-26 14:49 ` Tejun Heo
2013-09-26 15:46 ` Zhang Yanfei
2013-09-27 23:14 ` Toshi Kani
2013-09-24 18:35 ` [PATCH v5 6/6] mem-hotplug: Introduce movablenode boot option Zhang Yanfei
2013-09-26 14:53 ` Tejun Heo
2013-09-26 16:42 ` Zhang Yanfei
2013-09-27 6:26 ` Ingo Molnar [this message]
2013-09-27 8:08 ` Yanfei Zhang
2013-09-27 11:05 ` Ingo Molnar
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=20130927062633.GB6726@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gong.chen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=imtangchen@gmail.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=jweiner@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=lwoodman@redhat.com \
--cc=mgorman@suse.de \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=mingo@elte.hu \
--cc=prarit@redhat.com \
--cc=riel@redhat.com \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.com \
--cc=trenn@suse.de \
--cc=vasilis.liaskovitis@profitbricks.com \
--cc=wency@cn.fujitsu.com \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
--cc=zhangyanfei.yes@gmail.com \
--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