From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
tj@kernel.org, lizefan@huawei.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: Re: [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
Date: Mon, 15 Mar 2021 13:03:45 -0600 [thread overview]
Message-ID: <87im5s2q9a.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210313061029.28024-1-unixbhaskar@gmail.com>
Bhaskar Chowdhury <unixbhaskar@gmail.com> writes:
> s/overcommited/overcommitted/
> s/Overcommiting/Overcommitting/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Documentation/admin-guide/cgroup-v1/memory.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
> index 52688ae34461..0d574fd3f8e3 100644
> --- a/Documentation/admin-guide/cgroup-v1/memory.rst
> +++ b/Documentation/admin-guide/cgroup-v1/memory.rst
> @@ -360,8 +360,8 @@ U != 0, K = unlimited:
>
> U != 0, K < U:
> Kernel memory is a subset of the user memory. This setup is useful in
> - deployments where the total amount of memory per-cgroup is overcommited.
> - Overcommiting kernel memory limits is definitely not recommended, since the
> + deployments where the total amount of memory per-cgroup is overcommitted.
> + Overcommitting kernel memory limits is definitely not recommended, since the
> box can still run out of non-reclaimable memory.
Applied, thanks.
jon
prev parent reply other threads:[~2021-03-15 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 6:10 [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst Bhaskar Chowdhury
2021-03-13 6:51 ` Randy Dunlap
2021-03-15 19:03 ` 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=87im5s2q9a.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rdunlap@infradead.org \
--cc=tj@kernel.org \
--cc=unixbhaskar@gmail.com \
/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