From: Valentin Schneider <valentin.schneider@arm.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] sched/fair: Optimize select_idle_core
Date: Fri, 6 Dec 2019 16:57:37 +0000 [thread overview]
Message-ID: <8521e154-b485-c9fc-708d-7d87a12a9e9e@arm.com> (raw)
In-Reply-To: <20191206125317.GC22330@linux.vnet.ibm.com>
On 06/12/2019 12:53, Srikar Dronamraju wrote:
> Its probably something to think over. I probably don't have an answer on why
> we are not choosing the starting cpu to be primary CPU. Would we have to
> think of the case where the Primary CPUs are online / offline etc? I mean
> with target cpu, we know the CPU is online for sure.
>
Myes, CPU affinity also makes the thing much more painful (what if the task
is affined to some of the core's threads, but not the primary one?). The
current method has the merit of handling these cases.
prev parent reply other threads:[~2019-12-06 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 17:23 Srikar Dronamraju
2019-12-05 17:27 ` Vincent Guittot
2019-12-05 17:51 ` Srikar Dronamraju
2019-12-05 18:52 ` Vincent Guittot
2019-12-06 8:16 ` Srikar Dronamraju
2019-12-06 13:27 ` Vincent Guittot
2019-12-06 13:39 ` Srikar Dronamraju
2019-12-06 16:48 ` Vincent Guittot
2019-12-06 12:00 ` Valentin Schneider
2019-12-06 12:32 ` Peter Zijlstra
2019-12-06 12:53 ` Srikar Dronamraju
2019-12-06 16:57 ` Valentin Schneider [this message]
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=8521e154-b485-c9fc-708d-7d87a12a9e9e@arm.com \
--to=valentin.schneider@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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®