From: Jonathan Corbet <corbet@lwn.net>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tim Chen <tim.c.chen@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v2] Documentation, mm/unaccepted: document accept_memory kernel parameter
Date: Fri, 15 Dec 2023 09:30:05 -0700 [thread overview]
Message-ID: <871qbnqvhu.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231214-accept_memory_param-v2-1-f38cd20a0247@suse.cz>
Vlastimil Babka <vbabka@suse.cz> writes:
> 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.
>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> changes since v1:
> - use shorter sentences (Tim Chen)
> ---
> Documentation/admin-guide/kernel-parameters.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 65731b060e3f..91bd74b2e203 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1,3 +1,14 @@
> + accept_memory= [MM]
> + Format: { eager | lazy }
> + default: lazy
> + By default, unaccepted memory is accepted lazily to
> + avoid prolonged boot times. The lazy option will add
> + some runtime overhead until all memory is eventually
> + accepted. In most cases the overhead is negligible.
> + For some workloads or for debugging purposes
> + accept_memory=eager can be used to accept all memory
> + at once during boot.
> +
Applied, thanks.
jon
prev parent reply other threads:[~2023-12-15 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 12:22 [PATCH v2] Documentation, mm/unaccepted: document accept_memory kernel parameter Vlastimil Babka
2023-12-14 12:35 ` Vlastimil Babka
2023-12-15 16:30 ` Jonathan Corbet [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=871qbnqvhu.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
--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