Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 67de0162 authored by Jörg Sommer's avatar Jörg Sommer Committed by Linus Torvalds
Browse files

Documentation: fix cgroup typos and formatting 



Fix format and spelling.

Signed-off-by: default avatarJörg Sommer <joerg@alea.gnuu.de>
Acked-by: default avatarPaul Menage <menage@google.com>
Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent f6e07d38

Documentation/cgroups/blkio-controller.txt

+1 −1
Original line number Diff line number Diff line
@@ -111,7 +111,7 @@ Hierarchical Cgroups 
  CFQ and throttling will practically treat all groups at same level.



				pivot

			     /  |   \  \

			     /  /   \  \

			root  test1 test2  test3



  Down the line we can implement hierarchical accounting/control support

Documentation/cgroups/cgroups.txt

+1 −1
Original line number Diff line number Diff line
@@ -142,7 +142,7 @@ and depending on who is launching the browser he can 


With only a single hierarchy, he now would potentially have to create

a separate cgroup for every browser launched and associate it with

approp network and other resource class.  This may lead to

appropriate network and other resource class.  This may lead to

proliferation of such cgroups.



Also lets say that the administrator would like to give enhanced network

Documentation/cgroups/memory.txt

+11 −11
Original line number Diff line number Diff line 
Memory Resource Controller



NOTE: The Memory Resource Controller has been generically been referred

      to as the memory controller in this document. Do not confuse memory

      controller used here with the memory controller that is used in hardware.

NOTE: The Memory Resource Controller has generically been referred to as the

      memory controller in this document. Do not confuse memory controller

      used here with the memory controller that is used in hardware.



(For editors)

In this document:
@@ -182,7 +182,7 @@ behind this approach is that a cgroup that aggressively uses a shared 
page will eventually get charged for it (once it is uncharged from

the cgroup that brought it in -- this will happen on memory pressure).



Exception: If CONFIG_CGROUP_CGROUP_MEM_RES_CTLR_SWAP is not used..

Exception: If CONFIG_CGROUP_CGROUP_MEM_RES_CTLR_SWAP is not used.

When you do swapoff and make swapped-out pages of shmem(tmpfs) to

be backed into memory in force, charges for pages are accounted against the

caller of swapoff rather than the users of shmem.
@@ -214,7 +214,7 @@ affecting global LRU, memory+swap limit is better than just limiting swap from 
OS point of view.



* What happens when a cgroup hits memory.memsw.limit_in_bytes

When a cgroup his memory.memsw.limit_in_bytes, it's useless to do swap-out

When a cgroup hits memory.memsw.limit_in_bytes, it's useless to do swap-out

in this cgroup. Then, swap-out will not be done by cgroup routine and file

caches are dropped. But as mentioned above, global LRU can do swapout memory

from it for sanity of the system's memory management state. You can't forbid