From: Mike Kravetz <mike.kravetz@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] Documentation/admin-guide: kernel-parameters: update CMA entries
Date: Mon, 25 Jan 2021 13:59:20 -0800 [thread overview]
Message-ID: <1f116bc8-ce32-c746-3e7d-4fbd1ab33d3c@oracle.com> (raw)
In-Reply-To: <20210125043202.22399-1-rdunlap@infradead.org>
On 1/24/21 8:32 PM, Randy Dunlap wrote:
> Add qualifying build option legend [CMA] to kernel boot options
> that requirce CMA support to be enabled for them to be usable.
>
> Also capitalize 'CMA' when it is used as an acronym.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> ---
> v2: rebase & resend
>
> Documentation/admin-guide/kernel-parameters.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks,
Acked-by: Mike Kravetz <mike.kravetz@oracle.com>
--
Mike Kravetz
>
> --- linux-next-20210122.orig/Documentation/admin-guide/kernel-parameters.txt
> +++ linux-next-20210122/Documentation/admin-guide/kernel-parameters.txt
> @@ -631,7 +631,7 @@
> kernel/dma/contiguous.c
>
> cma_pernuma=nn[MG]
> - [ARM64,KNL]
> + [ARM64,KNL,CMA]
> Sets the size of kernel per-numa memory area for
> contiguous memory allocations. A value of 0 disables
> per-numa CMA altogether. And If this option is not
> @@ -1556,12 +1556,12 @@
> hpet_mmap= [X86, HPET_MMAP] Allow userspace to mmap HPET
> registers. Default set by CONFIG_HPET_MMAP_DEFAULT.
>
> - hugetlb_cma= [HW] The size of a cma area used for allocation
> + hugetlb_cma= [HW,CMA] The size of a CMA area used for allocation
> of gigantic hugepages.
> Format: nn[KMGTPE]
>
> - Reserve a cma area of given size and allocate gigantic
> - hugepages using the cma allocator. If enabled, the
> + Reserve a CMA area of given size and allocate gigantic
> + hugepages using the CMA allocator. If enabled, the
> boot-time allocation of gigantic hugepages is skipped.
>
> hugepages= [HW] Number of HugeTLB pages to allocate at boot.
>
next prev parent reply other threads:[~2021-01-25 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 4:32 [PATCH v2] Documentation/admin-guide: kernel-parameters: update CMA entries Randy Dunlap
2021-01-25 21:59 ` Mike Kravetz [this message]
2021-01-28 22:34 ` Jonathan Corbet
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=1f116bc8-ce32-c746-3e7d-4fbd1ab33d3c@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.