From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Nathan Fontenot <nfont@austin.ibm.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory hotplug disable boot option
Date: Fri, 25 Jun 2010 11:04:19 +0900 (JST) [thread overview]
Message-ID: <20100625105340.803C.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4C24012B.9030506@austin.ibm.com>
> Proposed patch to disable memory hotplug via a boot option,
> mem_hotplug=[on|off]. The patch only disables memory hotplug in that it
> prevents the creation of the memory sysfs directories for memory sections.
>
> This patch is meant to help alleviate very long boot times on systems with
> large memory (1+ TB) and many memory sections (10's of thousands).
Why making simple /sys file is so slowly? Couldn't we fix such performance
problem?
>
> Signed-off-by: Nathan Fontenot <nfont@austin.ibm.com>
>
> ---
> drivers/base/memory.c | 33 +++++++++++++++++++++++++++++++++
> drivers/base/node.c | 3 +++
> include/linux/memory.h | 2 ++
> 3 files changed, 38 insertions(+)
>
> Index: linux-2.6/drivers/base/memory.c
> ===================================================================
> --- linux-2.6.orig/drivers/base/memory.c 2010-06-23 15:07:03.000000000 -0500
> +++ linux-2.6/drivers/base/memory.c 2010-06-24 18:46:52.000000000 -0500
> @@ -29,6 +29,24 @@
>
> #define MEMORY_CLASS_NAME "memory"
>
> +static int mem_hp_enabled __read_mostly = 1;
please don't use 'hp' acronym. 'hotplug' is not so long word.
> +
> +static int __setup_memory_hotplug(char *option)
> +{
> + if (!strcmp(option, "off"))
> + mem_hp_enabled = 0;
> + else if (!strcmp(option, "on"))
> + mem_hp_enabled = 1;
> +
> + return 1;
> +}
> +__setup("mem_hotplug=", __setup_memory_hotplug);
no documentation on Documentation/kernel-parameters.txt?
next prev parent reply other threads:[~2010-06-25 2:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 1:06 Nathan Fontenot
2010-06-25 2:04 ` KOSAKI Motohiro [this message]
2010-06-25 9:19 ` Andi Kleen
2010-06-25 14:51 ` Nathan Fontenot
2010-06-25 14:56 ` Andi Kleen
2010-06-25 15:21 ` Nathan Fontenot
2010-06-25 15:28 ` Andi Kleen
2010-06-25 16:00 ` Nathan Fontenot
2010-06-28 2:20 ` KOSAKI Motohiro
2010-06-28 4:15 ` Eric W. Biederman
2010-06-28 14:16 ` Andi Kleen
2010-06-28 19:43 ` Eric W. Biederman
2010-06-28 15:02 ` Greg KH
2010-06-28 15:37 ` Nathan Fontenot
2010-06-28 15:44 ` Greg KH
2010-06-29 0:04 ` Dave Hansen
2010-06-29 2:56 ` KOSAKI Motohiro
2010-06-29 15:38 ` Nathan Fontenot
2010-06-30 0:00 ` KOSAKI Motohiro
2010-06-29 16:03 ` Dave Hansen
2010-06-29 18:04 ` Greg KH
2010-06-30 0:32 ` KAMEZAWA Hiroyuki
2010-06-30 15:47 ` Greg KH
2010-07-01 0:31 ` KAMEZAWA Hiroyuki
2010-07-01 3:17 ` Nathan Fontenot
2010-07-01 3:30 ` KAMEZAWA Hiroyuki
2010-07-01 23:28 ` Greg KH
2010-07-01 5:15 ` KAMEZAWA Hiroyuki
2010-07-01 13:23 ` Dave Hansen
2010-07-06 15:20 ` Nathan Fontenot
2010-07-06 15:33 ` Dave Hansen
2010-07-06 15:47 ` Nathan Fontenot
2010-07-01 23:26 ` Greg KH
2010-07-02 5:50 ` KAMEZAWA Hiroyuki
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=20100625105340.803C.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfont@austin.ibm.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
Powered by JetHome