From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH v2] sched/fair: fix imbalance due to CPU affinity
Date: Mon, 1 Jul 2019 21:03:58 +0200 [thread overview]
Message-ID: <20190701190358.GW3419@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1561996022-28829-1-git-send-email-vincent.guittot@linaro.org>
On Mon, Jul 01, 2019 at 05:47:02PM +0200, Vincent Guittot wrote:
> The load_balance() has a dedicated mecanism to detect when an imbalance
> is due to CPU affinity and must be handled at parent level. In this case,
> the imbalance field of the parent's sched_group is set.
>
> The description of sg_imbalanced() gives a typical example of two groups
> of 4 CPUs each and 4 tasks each with a cpumask covering 1 CPU of the first
> group and 3 CPUs of the second group. Something like:
>
> { 0 1 2 3 } { 4 5 6 7 }
> * * * *
>
> But the load_balance fails to fix this UC on my octo cores system
> made of 2 clusters of quad cores.
>
> Whereas the load_balance is able to detect that the imbalanced is due to
> CPU affinity, it fails to fix it because the imbalance field is cleared
> before letting parent level a chance to run. In fact, when the imbalance is
> detected, the load_balance reruns without the CPU with pinned tasks. But
> there is no other running tasks in the situation described above and
> everything looks balanced this time so the imbalance field is immediately
> cleared.
>
> The imbalance field should not be cleared if there is no other task to move
> when the imbalance is detected.
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Thanks!
next prev parent reply other threads:[~2019-07-01 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 15:47 Vincent Guittot
2019-07-01 19:03 ` Peter Zijlstra [this message]
2019-07-02 9:34 ` Valentin Schneider
2019-07-02 10:00 ` Vincent Guittot
2019-07-02 14:29 ` Valentin Schneider
2019-07-05 12:23 ` Vincent Guittot
2019-07-25 16:13 ` [tip:sched/core] sched/fair: Fix " tip-bot for Vincent Guittot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190701190358.GW3419@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®