From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] sched/fair: don't set LBF_ALL_PINNED unnecessarily
Date: Wed, 6 Jan 2021 16:32:47 +0100 [thread overview]
Message-ID: <X/XYHxPtGFhJe+bu@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtB+Nrk6ST9c-OacdW3zh07VC6M8GqvgNXzQ=KqucBrqQQ@mail.gmail.com>
On Wed, Jan 06, 2021 at 04:20:55PM +0100, Vincent Guittot wrote:
> This case here is :
> we have 2 tasks TA and TB on the rq.
> The waiting one TB can't migrate for a reason other than the pinned case.
> We decide to start the active migration on the running TA task but TA
> is pinned.
> In this case we are not in the all pinned case.
But then can_migrate_task(TB) should clear ALL_PINNED, no?
next prev parent reply other threads:[~2021-01-06 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 13:34 [PATCH 0/3] Reduce number of active LB Vincent Guittot
2021-01-06 13:34 ` [PATCH 1/3] sched/fair: skip idle cfs_rq Vincent Guittot
2021-01-06 15:13 ` Valentin Schneider
2021-01-06 13:34 ` [PATCH 2/3] sched/fair: don't set LBF_ALL_PINNED unnecessarily Vincent Guittot
2021-01-06 15:07 ` Peter Zijlstra
2021-01-06 15:20 ` Vincent Guittot
2021-01-06 15:32 ` Peter Zijlstra [this message]
2021-01-06 15:45 ` Vincent Guittot
2021-01-06 15:13 ` Valentin Schneider
2021-01-06 16:04 ` Vincent Guittot
2021-01-06 13:34 ` [PATCH 3/3] sched/fair: reduce cases for active balance Vincent Guittot
2021-01-06 15:13 ` Peter Zijlstra
2021-01-06 15:41 ` Vincent Guittot
2021-01-06 16:11 ` Peter Zijlstra
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=X/XYHxPtGFhJe+bu@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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