* [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
@ 2021-03-13 6:10 Bhaskar Chowdhury
[not found] ` <20210313061029.28024-1-unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Bhaskar Chowdhury @ 2021-03-13 6:10 UTC (permalink / raw)
To: tj-DgEjT+Ai2ygdnm+yROfE0A, lizefan-hv44wF8Li93QT0dZR+AlfA,
hannes-druUgvl0LCNAfugRpC6u6w, corbet-T1hC0tSOHrs,
cgroups-u79uwXL29TY76Z2rM5mHXA, linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
Cc: rdunlap-wEGCiKHe2LqWVfeAwA7xHQ, Bhaskar Chowdhury
s/overcommited/overcommitted/
s/Overcommiting/Overcommitting/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
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.
In this case, the admin could set up K so that the sum of all groups is
never greater than the total memory, and freely set U at the cost of his
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
[not found] ` <20210313061029.28024-1-unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2021-03-13 6:51 ` Randy Dunlap
2021-03-15 19:03 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2021-03-13 6:51 UTC (permalink / raw)
To: Bhaskar Chowdhury, tj-DgEjT+Ai2ygdnm+yROfE0A,
lizefan-hv44wF8Li93QT0dZR+AlfA, hannes-druUgvl0LCNAfugRpC6u6w,
corbet-T1hC0tSOHrs, cgroups-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
On 3/12/21 10:10 PM, Bhaskar Chowdhury wrote:
>
> s/overcommited/overcommitted/
> s/Overcommiting/Overcommitting/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Acked-by: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
> ---
> 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.
> In this case, the admin could set up K so that the sum of all groups is
> never greater than the total memory, and freely set U at the cost of his
> --
--
~Randy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
[not found] ` <20210313061029.28024-1-unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-03-13 6:51 ` Randy Dunlap
@ 2021-03-15 19:03 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2021-03-15 19:03 UTC (permalink / raw)
To: Bhaskar Chowdhury, tj-DgEjT+Ai2ygdnm+yROfE0A,
lizefan-hv44wF8Li93QT0dZR+AlfA, hannes-druUgvl0LCNAfugRpC6u6w,
cgroups-u79uwXL29TY76Z2rM5mHXA, linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
Cc: rdunlap-wEGCiKHe2LqWVfeAwA7xHQ, Bhaskar Chowdhury
Bhaskar Chowdhury <unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> s/overcommited/overcommitted/
> s/Overcommiting/Overcommitting/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-03-15 19:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-13 6:10 [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst Bhaskar Chowdhury
[not found] ` <20210313061029.28024-1-unixbhaskar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-03-13 6:51 ` Randy Dunlap
2021-03-15 19:03 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox