From: Randy Dunlap <rdunlap@infradead.org>
To: Sudarshan Rajagopalan <sudaraja@codeaurora.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] arm64: make section size configurable for memory hotplug
Date: Tue, 5 Jan 2021 18:20:40 -0800 [thread overview]
Message-ID: <1c4613bc-56e9-de99-e9de-4313b4aa88a2@infradead.org> (raw)
In-Reply-To: <66f79b0c06602c22df4da8ff4a5c2b97c9275250.1609895500.git.sudaraja@codeaurora.org>
On 1/5/21 5:28 PM, Sudarshan Rajagopalan wrote:
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 6d232837cbee..34124eee65da 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -294,6 +294,17 @@ config ARCH_ENABLE_MEMORY_HOTREMOVE
> config SMP
> def_bool y
>
> +config HOTPLUG_SIZE_BITS
> + int "Memory hotplug block size(29 => 512MB 30 => 1GB)"
block size (29 => 512MB, 30 => 1GB)"
> + depends on SPARSEMEM
> + depends on MEMORY_HOTPLUG
> + range 28 30
> + default 30
> + help
> + Selects granularity of hotplug memory. Block size for
> + memory hotplug is represent as a power of 2.
represented
> + If unsure, stick with default value.
and all of the help text should be indented with 1 tab + 2 spaces.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-01-06 2:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 1:28 [PATCH 0/1] arm64: make section size configurable for memory hotplug Sudarshan Rajagopalan
2021-01-06 1:28 ` [PATCH 1/1] " Sudarshan Rajagopalan
2021-01-06 2:20 ` Randy Dunlap [this message]
2021-01-06 6:11 ` Anshuman Khandual
2021-01-07 12:30 ` David Hildenbrand
2021-01-08 7:02 ` Anshuman Khandual
2021-01-08 15:30 ` David Hildenbrand
2021-01-11 4:17 ` Anshuman Khandual
2021-01-11 10:13 ` David Hildenbrand
2021-01-11 10:26 ` Anshuman Khandual
2021-01-08 1:01 ` Sudarshan Rajagopalan
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=1c4613bc-56e9-de99-e9de-4313b4aa88a2@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sudaraja@codeaurora.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;
as well as URLs for NNTP newsgroup(s).