Re: [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
Bhaskar Chowdhury writes: > s/overcommited/overcommitted/ > s/Overcommiting/Overcommitting/ > > Signed-off-by: Bhaskar Chowdhury > --- > 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
Re: [PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
On 3/12/21 10:10 PM, Bhaskar Chowdhury wrote: > > s/overcommited/overcommitted/ > s/Overcommiting/Overcommitting/ > > Signed-off-by: Bhaskar Chowdhury Acked-by: Randy Dunlap > --- > 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
[PATCH] docs: admin-guide: cgroup-v1: Fix typos in the file memory.rst
s/overcommited/overcommitted/ s/Overcommiting/Overcommitting/ Signed-off-by: Bhaskar Chowdhury --- 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 -- 2.26.2
