All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Perret <qperret@google.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	linux-kernel@vger.kernel.org,
	Valentin Schneider <valentin.schneider@arm.com>,
	Morten Rasmussen <morten.rasmussen@arm.com>
Subject: Re: [PATCH] sched/eas: Don't update misfit status if the task is pinned
Date: Tue, 19 Jan 2021 17:50:22 +0000	[thread overview]
Message-ID: <YAcb3vUFovqz1gCL@google.com> (raw)
In-Reply-To: <20210119174244.3p2graxd5gonv4di@e107158-lin>

On Tuesday 19 Jan 2021 at 17:42:44 (+0000), Qais Yousef wrote:
> Hmm IIUC you want to still tag it as misfit so it'll be balanced within the
> little cores in case there's another core with more spare capacity, right?

Well yes but that's just a special case. But even you have big CPUs in
the affinity mask, you may find that the task fits on none of the CPUs
because they're currently under pressure. But in this case, you may
still want to mark the task as misfit because being under pressure may
be a relatively transient state.

  reply	other threads:[~2021-01-19 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 12:07 [PATCH] sched/eas: Don't update misfit status if the task is pinned Qais Yousef
2021-01-19 12:24 ` Valentin Schneider
2021-01-19 13:34 ` Vincent Guittot
2021-01-19 13:54   ` Valentin Schneider
2021-01-19 14:19     ` Vincent Guittot
2021-01-19 16:55       ` Valentin Schneider
2021-01-19 17:06         ` Vincent Guittot
2021-01-19 15:35 ` Quentin Perret
2021-01-19 16:40   ` Qais Yousef
2021-01-19 16:55     ` Quentin Perret
2021-01-19 17:42       ` Qais Yousef
2021-01-19 17:50         ` Quentin Perret [this message]
2021-01-20 11:57           ` Qais Yousef

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=YAcb3vUFovqz1gCL@google.com \
    --to=qperret@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=qais.yousef@arm.com \
    --cc=valentin.schneider@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.