housekeeping: Document isolcpus flags
PATCH v7 1/1 housekeeping: Document isolcpus flags
Document the latest updates on the isolcpus boot option. While at it, let's also fix the details about the preferred way to isolate a set of CPUs from the scheduler general domains. Cpusets offer a much better interface to achieve that.
Signed-off-by Frederic Weisbecker <[email protected]>
Cc Chris Metcalf <[email protected]>
Cc Rik van Riel <[email protected]>
Cc Peter Zijlstra <[email protected]>
Cc Thomas Gleixner <[email protected]>
Cc Mike Galbraith <[email protected]>
Cc Ingo Molnar <[email protected]>
Cc Christoph Lameter <[email protected]>
Cc Paul E. McKenney <[email protected]>
Cc Wanpeng Li <[email protected]>
Cc Luiz Capitulino <[email protected]>
--- Documentation/admin-guide/kernel-parameters.txt | 40 ++++++++++++++++--------- 1 file changed, 26 insertions(+), 14 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +26 -14
@@ -1727,20 +1727,32 @@ isapnp= [ISAPNP] Format: <RDP>,<reset>,<pci_scan>,<verbosity> - isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler. - The argument is a cpu list, as described above. - - This option can be used to specify one or more CPUs - to isolate from the general SMP balancing and scheduling - algorithms. You can move a process onto or off an - "isolated" CPU via the CPU affinity syscalls or cpuset. - <cpu number> begins at 0 and the maximum value is - "number of CPUs in system - 1". - - This option is the preferred way to isolate CPUs. The - alternative -- manually setting the CPU mask of all - tasks in the system -- can cause problems and - suboptimal load balancer performance. + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance. + Format: [flag-list,]<cpu-list> + + Specify one or more CPUs to isolate from disturbances + specified in the flag list (default: domain): + + nohz + Disable the tick when a single task runs. + domain + Isolate from the general SMP balancing and scheduling + algorithms. Note that performing domain isolation this way + is irreversible. It's not possible to bring back a CPU to + the domains once isolated through isolcpus. It's strongly + advised to use Cpusets instead to disable scheduler load + balancing through the file "cpuset.sched_load_balance". + It offers a much more flexible interface where CPUs can + move in and out of an isolated set anytime. + + You can move a process onto or off an "isolated" CPU via + the CPU affinity syscalls or cpuset. + <cpu number> begins at 0 and the maximum value is + "number of CPUs in system - 1". + + The format of <cpu-list> is described above. + + iucv= [HW,NET]
Signature · 1 line
2.7.4
tip-bot for Frederic Weisbecker
merge bot[tip:sched/core] sched/isolation: Document isolcpus= boot parameter flags, mark it deprecated
sched/isolation: Document isolcpus= boot parameter flags, mark it deprecated
Commit-ID: b0d40d2b22fe48cfcbbfb137fd198be0a1cd8a85 Gitweb: https://git.kernel.org/tip/b0d40d2b22fe48cfcbbfb137fd198be0a1cd8a85 Author: Frederic Weisbecker <[email protected]> AuthorDate: Tue, 31 Oct 2017 04:18:34 +0100 Committer: Ingo Molnar <[email protected]> CommitDate: Tue, 31 Oct 2017 10:29:39 +0100
sched/isolation: Document isolcpus= boot parameter flags, mark it deprecated
Document the latest updates on the isolcpus= boot option. While at it, let's also fix the details about the preferred way to isolate a set of CPUs from the scheduler general domains. Cpusets offer a much better interface to achieve that.
Signed-off-by Frederic Weisbecker <[email protected]>
Acked-by Thomas Gleixner <[email protected]>
Acked-by Peter Zijlstra <[email protected]>
Cc Chris Metcalf <[email protected]>
Cc Christoph Lameter <[email protected]>
Cc Linus Torvalds <[email protected]>
Cc Luiz Capitulino <[email protected]>
Cc Mike Galbraith <[email protected]>
Cc Paul E. McKenney <[email protected]>
Cc Rik van Riel <[email protected]>
Cc Wanpeng Li <[email protected]>
[ Clarified the text some more, marked the boot option deprecated. ]
Signed-off-by Ingo Molnar <[email protected]>
--- Documentation/admin-guide/kernel-parameters.txt | 39 ++++++++++++++++--------- 1 file changed, 26 insertions(+), 13 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +26 -13
@@ -1727,20 +1727,33 @@ isapnp= [ISAPNP] Format: <RDP>,<reset>,<pci_scan>,<verbosity> - isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler. - The argument is a cpu list, as described above. + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance. + [Deprecated - use cpusets instead] + Format: [flag-list,]<cpu-list> + + Specify one or more CPUs to isolate from disturbances + specified in the flag list (default: domain): + + nohz + Disable the tick when a single task runs. + domain + Isolate from the general SMP balancing and scheduling + algorithms. Note that performing domain isolation this way + is irreversible: it's not possible to bring back a CPU to + the domains once isolated through isolcpus. It's strongly + advised to use cpusets instead to disable scheduler load + balancing through the "cpuset.sched_load_balance" file. + It offers a much more flexible interface where CPUs can + move in and out of an isolated set anytime. + + You can move a process onto or off an "isolated" CPU via + the CPU affinity syscalls or cpuset. + <cpu number> begins at 0 and the maximum value is + "number of CPUs in system - 1". + + The format of <cpu-list> is described above. + - This option can be used to specify one or more CPUs - to isolate from the general SMP balancing and scheduling - algorithms. You can move a process onto or off an - "isolated" CPU via the CPU affinity syscalls or cpuset. - <cpu number> begins at 0 and the maximum value is - "number of CPUs in system - 1". - - This option is the preferred way to isolate CPUs. The - alternative -- manually setting the CPU mask of all - tasks in the system -- can cause problems and - suboptimal load balancer performance. iucv= [HW,NET]