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

Commit 21acb9ca authored by Thadeu Lima de Souza Cascardo's avatar Thadeu Lima de Souza Cascardo Committed by Jiri Kosina
Browse files

trivial: fix where cgroup documentation is not correctly referred to 



cgroup documentation was moved to Documentation/cgroups/. There are some
places that still refer to Documentation/controllers/,
Documentation/cgroups.txt and Documentation/cpusets.txt. Fix those.

Signed-off-by: default avatarThadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Reviewed-by: default avatarLi Zefan <lizf@cn.fujitsu.com>
Acked-by: default avatarPaul Menage <menage@google.com>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent 6d5e147d

Documentation/00-INDEX

+2 −2
Original line number Diff line number Diff line
@@ -86,6 +86,8 @@ cachetlb.txt 
	- describes the cache/TLB flushing interfaces Linux uses.

cdrom/

	- directory with information on the CD-ROM drivers that Linux has.

cgroups/

	- cgroups features, including cpusets and memory controller.

connector/

	- docs on the netlink based userspace<->kernel space communication mod.

console/
@@ -98,8 +100,6 @@ cpu-load.txt 
	- document describing how CPU load statistics are collected.

cpuidle/

	- info on CPU_IDLE, CPU idle state management subsystem.

cpusets.txt

	- documents the cpusets feature; assign CPUs and Mem to a set of tasks.

cputopology.txt

	- documentation on how CPU topology info is exported via sysfs.

cris/

Documentation/cgroups/00-INDEX

0 → 100644
+18 −0
Original line number Diff line number Diff line 
00-INDEX

	- this file

cgroups.txt

	- Control Groups definition, implementation details, examples and API.

cpuacct.txt

	- CPU Accounting Controller; account CPU usage for groups of tasks.

cpusets.txt

	- documents the cpusets feature; assign CPUs and Mem to a set of tasks.

devices.txt

	- Device Whitelist Controller; description, interface and security.

freezer-subsystem.txt

	- checkpointing; rationale to not use signals, interface.

memcg_test.txt

	- Memory Resource Controller; implementation details.

memory.txt

	- Memory Resource Controller; design, accounting, interface, testing.

resource_counter.txt

	- Resource Counter API.

Documentation/kernel-parameters.txt

+2 −2
Original line number Diff line number Diff line
@@ -1593,7 +1593,7 @@ and is between 256 and 4096 characters. It is defined in the file 
	nosoftlockup	[KNL] Disable the soft-lockup detector.



	noswapaccount	[KNL] Disable accounting of swap in memory resource

			controller. (See Documentation/controllers/memory.txt)

			controller. (See Documentation/cgroups/memory.txt)



	nosync		[HW,M68K] Disables sync negotiation for all devices.
@@ -1932,7 +1932,7 @@ and is between 256 and 4096 characters. It is defined in the file 


	relax_domain_level=

			[KNL, SMP] Set scheduler's default relax_domain_level.

			See Documentation/cpusets.txt.

			See Documentation/cgroups/cpusets.txt.



	reserve=	[KNL,BUGS] Force the kernel to ignore some iomem area

Documentation/scheduler/sched-rt-group.txt

+1 −1
Original line number Diff line number Diff line
@@ -126,7 +126,7 @@ This uses the /cgroup virtual file system and "/cgroup/<cgroup>/cpu.rt_runtime_u 
to control the CPU time reserved for each control group instead.



For more information on working with control groups, you should read

Documentation/cgroups.txt as well.

Documentation/cgroups/cgroups.txt as well.



Group settings are checked against the following limits in order to keep the configuration

schedulable:

Documentation/vm/numa_memory_policy.txt

+2 −1
Original line number Diff line number Diff line
@@ -8,7 +8,8 @@ The current memory policy support was added to Linux 2.6 around May 2004. This 
document attempts to describe the concepts and APIs of the 2.6 memory policy

support.



Memory policies should not be confused with cpusets (Documentation/cpusets.txt)

Memory policies should not be confused with cpusets

(Documentation/cgroups/cpusets.txt)

which is an administrative mechanism for restricting the nodes from which

memory may be allocated by a set of processes. Memory policies are a

programming interface that a NUMA-aware application can take advantage of.  When