Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1632889 > unrolled thread

[PATCH 03/14] sched/topology: Fix building of overlapping sched-groups

Started byPeter Zijlstra <peterz@infradead.org>
First post2017-04-28 15:40 +0200
Last post2017-05-01 22:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [PATCH 03/14] sched/topology: Fix building of overlapping sched-groups Peter Zijlstra <peterz@infradead.org> - 2017-04-28 15:40 +0200
    Re: [PATCH 03/14] sched/topology: Fix building of overlapping  sched-groups Rik van Riel <riel@redhat.com> - 2017-05-01 22:10 +0200

#1632889 — [PATCH 03/14] sched/topology: Fix building of overlapping sched-groups

FromPeter Zijlstra <peterz@infradead.org>
Date2017-04-28 15:40 +0200
Subject[PATCH 03/14] sched/topology: Fix building of overlapping sched-groups
Message-ID<tBehQ-7VW-39@gated-at.bofh.it>
When building the overlapping groups, we very obviously should start
with the previous domain of _this_ @cpu, not CPU-0.

This can be readily demonstrated with a topology like:

  node   0   1   2   3
    0:  10  20  30  20
    1:  20  10  20  30
    2:  30  20  10  20
    3:  20  30  20  10

Where (for example) CPU1 ends up generating the following nonsensical groups:

  [] CPU1 attaching sched-domain:
  []  domain 0: span 0-2 level NUMA
  []   groups: 1 2 0
  []   domain 1: span 0-3 level NUMA
  []    groups: 1-3 (cpu_capacity = 3072) 0-1,3 (cpu_capacity = 3072)

Where the fact that domain 1 doesn't include a group with span 0-2 is
the obvious fail.

With patch this looks like:

  [] CPU1 attaching sched-domain:
  []  domain 0: span 0-2 level NUMA
  []   groups: 1 0 2
  []   domain 1: span 0-3 level NUMA
  []    groups: 0-2 (cpu_capacity = 3072) 0,2-3 (cpu_capacity = 3072)

Cc: stable@vger.kernel.org
Fixes: e3589f6c81e4 ("sched: Allow for overlapping sched_domain spans")
Debugged-by: Lauro Ramos Venancio <lvenanci@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
 kernel/sched/topology.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/kernel/sched/topology.c
+++ b/kernel/sched/topology.c
@@ -525,7 +525,7 @@ build_overlap_sched_groups(struct sched_
 
 	cpumask_clear(covered);
 
-	for_each_cpu(i, span) {
+	for_each_cpu_wrap(i, span, cpu) {
 		struct cpumask *sg_span;
 
 		if (cpumask_test_cpu(i, covered))

[toc] | [next] | [standalone]


#1633848 — Re: [PATCH 03/14] sched/topology: Fix building of overlapping sched-groups

FromRik van Riel <riel@redhat.com>
Date2017-05-01 22:10 +0200
SubjectRe: [PATCH 03/14] sched/topology: Fix building of overlapping sched-groups
Message-ID<tCpNT-59h-5@gated-at.bofh.it>
In reply to#1632889
On Fri, 2017-04-28 at 15:20 +0200, Peter Zijlstra wrote:
> When building the overlapping groups, we very obviously should start
> with the previous domain of _this_ @cpu, not CPU-0.

> With patch this looks like:
> 
>   [] CPU1 attaching sched-domain:
>   []  domain 0: span 0-2 level NUMA
>   []   groups: 1 0 2
>   []   domain 1: span 0-3 level NUMA
>   []    groups: 0-2 (cpu_capacity = 3072) 0,2-3 (cpu_capacity = 3072)
> 
> Cc: stable@vger.kernel.org
> Fixes: e3589f6c81e4 ("sched: Allow for overlapping sched_domain
> spans")
> Debugged-by: Lauro Ramos Venancio <lvenanci@redhat.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>

Acked-by: Rik van Riel <riel@redhat.com>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web