linux-kernel - Re: [PATCH v2] Documentation, mm/unaccepted: document accept

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <871qbnqvhu.fsf@meer.lwn.net>
Date: Fri, 15 Dec 2023 09:30:05 -0700
From: Jonathan Corbet <corbet@....net>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Tim Chen
 <tim.c.chen@...ux.intel.com>, "Kirill A. Shutemov"
 <kirill.shutemov@...ux.intel.com>, Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH v2] Documentation, mm/unaccepted: document accept_memory
 kernel parameter

Vlastimil Babka <vbabka@...e.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@...ux.intel.com>
> Signed-off-by: Vlastimil Babka <vbabka@...e.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