Re: [PATCH 3/2] cpusets,isolcpus: document relationship between cpusets & isolcpus
On 2015/2/28 1:08, Rik van Riel wrote: > Document the subtly changed relationship between cpusets and isolcpus. > Turns out the old documentation did not quite match the code... > > Signed-off-by: Rik van Riel > Suggested-by: Peter Zijlstra Acked-by: Zefan Li -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 3/2] cpusets,isolcpus: document relationship between cpusets & isolcpus
On Fri, 27 Feb 2015, Rik van Riel wrote: > Document the subtly changed relationship between cpusets and isolcpus. > Turns out the old documentation did not quite match the code... > > Signed-off-by: Rik van Riel > Suggested-by: Peter Zijlstra Acked-by: David Rientjes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 3/2] cpusets,isolcpus: document relationship between cpusets & isolcpus
Document the subtly changed relationship between cpusets and isolcpus. Turns out the old documentation did not quite match the code... Signed-off-by: Rik van Riel Suggested-by: Peter Zijlstra --- Documentation/cgroups/cpusets.txt | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/Documentation/cgroups/cpusets.txt b/Documentation/cgroups/cpusets.txt index f2235a162529..fdf7dff3f607 100644 --- a/Documentation/cgroups/cpusets.txt +++ b/Documentation/cgroups/cpusets.txt @@ -392,8 +392,10 @@ Put simply, it costs less to balance between two smaller sched domains than one big one, but doing so means that overloads in one of the two domains won't be load balanced to the other one. -By default, there is one sched domain covering all CPUs, except those -marked isolated using the kernel boot time "isolcpus=" argument. +By default, there is one sched domain covering all CPUs, including those +marked isolated using the kernel boot time "isolcpus=" argument. However, +the isolated CPUs will not participate in load balancing, and will not +have tasks running on them unless explicitly assigned. This default load balancing across all CPUs is not well suited for the following two situations: @@ -465,6 +467,10 @@ such partially load balanced cpusets, as they may be artificially constrained to some subset of the CPUs allowed to them, for lack of load balancing to the other CPUs. +CPUs in "cpuset.isolcpus" were excluded from load balancing by the +isolcpus= kernel boot option, and will never be load balanced regardless +of the value of "cpuset.sched_load_balance" in any cpuset. + 1.7.1 sched_load_balance implementation details. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 3/2] cpusets,isolcpus: document relationship between cpusets isolcpus
On 2015/2/28 1:08, Rik van Riel wrote: Document the subtly changed relationship between cpusets and isolcpus. Turns out the old documentation did not quite match the code... Signed-off-by: Rik van Riel r...@redhat.com Suggested-by: Peter Zijlstra pet...@infradead.org Acked-by: Zefan Li lize...@huawei.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 3/2] cpusets,isolcpus: document relationship between cpusets isolcpus
Document the subtly changed relationship between cpusets and isolcpus. Turns out the old documentation did not quite match the code... Signed-off-by: Rik van Riel r...@redhat.com Suggested-by: Peter Zijlstra pet...@infradead.org --- Documentation/cgroups/cpusets.txt | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/Documentation/cgroups/cpusets.txt b/Documentation/cgroups/cpusets.txt index f2235a162529..fdf7dff3f607 100644 --- a/Documentation/cgroups/cpusets.txt +++ b/Documentation/cgroups/cpusets.txt @@ -392,8 +392,10 @@ Put simply, it costs less to balance between two smaller sched domains than one big one, but doing so means that overloads in one of the two domains won't be load balanced to the other one. -By default, there is one sched domain covering all CPUs, except those -marked isolated using the kernel boot time isolcpus= argument. +By default, there is one sched domain covering all CPUs, including those +marked isolated using the kernel boot time isolcpus= argument. However, +the isolated CPUs will not participate in load balancing, and will not +have tasks running on them unless explicitly assigned. This default load balancing across all CPUs is not well suited for the following two situations: @@ -465,6 +467,10 @@ such partially load balanced cpusets, as they may be artificially constrained to some subset of the CPUs allowed to them, for lack of load balancing to the other CPUs. +CPUs in cpuset.isolcpus were excluded from load balancing by the +isolcpus= kernel boot option, and will never be load balanced regardless +of the value of cpuset.sched_load_balance in any cpuset. + 1.7.1 sched_load_balance implementation details. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 3/2] cpusets,isolcpus: document relationship between cpusets isolcpus
On Fri, 27 Feb 2015, Rik van Riel wrote: Document the subtly changed relationship between cpusets and isolcpus. Turns out the old documentation did not quite match the code... Signed-off-by: Rik van Riel r...@redhat.com Suggested-by: Peter Zijlstra pet...@infradead.org Acked-by: David Rientjes rient...@google.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
