From: Tim Chen <tim.c.chen@linux.intel.com>
To: Vlastimil Babka <vbabka@suse.cz>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] Documentation, mm/unaccepted: document accept_memory kernel parameter
Date: Tue, 12 Dec 2023 15:10:07 -0800 [thread overview]
Message-ID: <b3c71b866bb249107ed2920e31a7ec185b2f0b15.camel@linux.intel.com> (raw)
In-Reply-To: <20231212-accept_memory_param-v1-1-a9012402b887@suse.cz>
On Tue, 2023-12-12 at 18:21 +0100, Vlastimil Babka wrote:
> The accept_memory kernel parameter was added in commit dcdfdd40fa82
> ("mm: Add support for unaccepted memory") but not listed in the
> kernel-parameters doc. Add it there.
>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 65731b060e3f..3a4ebb46073c 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1,3 +1,13 @@
> + accept_memory= [MM]
> + Format: { eager | lazy }
> + default: lazy
> + By default, unaccepted memory is accepted lazily to
> + avoid prolonged boot at the cost of some runtime
Suggest rephrasing this line. Breaking up long line makes reading easier.
avoid prolonged boot. The lazy option will add some runtime
Thanks.
Tim
> + overhead until all memory is eventually accepted. In
> + most cases the overhead is negligible but for some
> + workloads or for debugging purposes accept_memory=eager
> + can be used to accept all memory at once during boot.
> +
> acpi= [HW,ACPI,X86,ARM64,RISCV64]
> Advanced Configuration and Power Interface
> Format: { force | on | off | strict | noirq | rsdt |
>
> ---
> base-commit: a39b6ac3781d46ba18193c9dbb2110f31e9bffe9
> change-id: 20231212-accept_memory_param-4a7adc5e5582
>
> Best regards,
prev parent reply other threads:[~2023-12-12 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:21 Vlastimil Babka
2023-12-12 22:40 ` Kirill A. Shutemov
2023-12-12 23:10 ` Tim Chen [this message]
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=b3c71b866bb249107ed2920e31a7ec185b2f0b15.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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