From: Jonathan Corbet <corbet@lwn.net>
To: Robert Elliott <elliott@hpe.com>
Cc: akpm@linux-foundation.org, mgorman@techsingularity.net,
matt@codeblueprint.co.uk, linux-doc@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/kernel-parameters: update KMG units
Date: Sun, 27 Dec 2015 03:58:10 -0700 [thread overview]
Message-ID: <20151227035810.0c408e2d@lwn.net> (raw)
In-Reply-To: <1450917496-4023-1-git-send-email-elliott@hpe.com>
On Wed, 23 Dec 2015 18:38:16 -0600
Robert Elliott <elliott@hpe.com> wrote:
> Since commit e004f3c7780d ("lib/cmdline.c: add size unit t/p/e to
> memparse") expanded memparse() to support T, P, and E units in addition
> to K, M, and G, all the kernel parameters that use that function became
> capable of more than [KMG] mentioned in kernel-parameters.txt.
>
> Expand the introduction to the units and change all existing [KMG]
> descriptions to [KMGTPE]. cma only had [MG]; reservelow only had [K].
>
> Add [KMGTPE] for hugepagesz and memory_corruption_check_size, which also
> use memparse().
>
> Update two source code files with comments mentioning [KMG].
This one, too, goes outside of the docs tree, but it seems obvious enough
and I'll take the liberty of applying it. Hopefully Andrew and company
won't get too upset if I touch page_alloc.c...
Thanks,
jon
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-12-27 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 0:38 [PATCH] Documentation/kernel-parameters: update KMG units Robert Elliott
2015-12-27 10:58 ` Jonathan Corbet [this message]
2016-01-12 1:31 ` 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=20151227035810.0c408e2d@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=elliott@hpe.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
/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).