Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1624714
| From | Lauro Venancio <lvenanci@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu |
| Date | 2017-04-17 17:40 +0200 |
| Message-ID | <txgUV-2mc-3@gated-at.bofh.it> (permalink) |
| References | <tvNrX-3KR-5@gated-at.bofh.it> <tvNrY-3KR-29@gated-at.bofh.it> <twcA2-3pr-17@gated-at.bofh.it> |
| Organization | Red Hat |
On 04/14/2017 01:49 PM, Peter Zijlstra wrote: > On Thu, Apr 13, 2017 at 10:56:09AM -0300, Lauro Ramos Venancio wrote: >> Currently, the group balance cpu is the groups's first CPU. But with >> overlapping groups, two different groups can have the same first CPU. >> >> This patch uses the group mask to mark all the CPUs that have a >> particular group as its main sched group. The group balance cpu is the >> first group CPU that is also in the mask. > Please give a NUMA configuration and CPU number where this goes wrong. On a 4 nodes with ring topology, the groups (0-1,3 [cpu 0]), (0-2 [cpu 1]) and (0,2-3 [cpu 3]) share the same sched_group_capacity instance when the first groups cpu is used to select the sgc. > > Because only the first group of a domain matters, and with the other > thing fixed, I'm not immediately seeing where we go wobbly. Before patch 2, the group balance cpu was implicitly used to select the sched_group_capacity instance. When two different groups had the same balance cpu, they shared the same sched_group_capacity instance. After patch 2, one different sched_group_capacity instance is assigned to each group instance. This patch ensures tree things: 1) different instances of the same group share the same sched_group_capacity instance. 2) instances of different groups don't share the same sched_group_capacity instance. 3) the group balance cpu must be one of the cpus where the group is installed. I am rebasing this patch on top of your patches.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC 0/3] sched/topology: fix sched groups on NUMA machines with mesh topology Lauro Ramos Venancio <lvenanci@redhat.com> - 2017-04-13 16:00 +0200
[RFC 1/3] sched/topology: Refactor function build_overlap_sched_groups() Lauro Ramos Venancio <lvenanci@redhat.com> - 2017-04-13 16:00 +0200
Re: [RFC 1/3] sched/topology: Refactor function build_overlap_sched_groups() Rik van Riel <riel@redhat.com> - 2017-04-13 17:00 +0200
[RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu Lauro Ramos Venancio <lvenanci@redhat.com> - 2017-04-13 16:00 +0200
Re: [RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu Rik van Riel <riel@redhat.com> - 2017-04-13 17:30 +0200
Re: [RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu Peter Zijlstra <peterz@infradead.org> - 2017-04-14 18:50 +0200
Re: [RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu Lauro Venancio <lvenanci@redhat.com> - 2017-04-17 17:40 +0200
Re: [RFC 3/3] sched/topology: Different sched groups must not have the same balance cpu Peter Zijlstra <peterz@infradead.org> - 2017-04-18 14:40 +0200
csiph-web