public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: peterz@infradead.org
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Jiang Biao <benbjiang@gmail.com>, 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>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jiang Biao <benbjiang@tencent.com>
Subject: Re: [PATCH] sched/fair: avoid vruntime compensation for SCHED_IDLE task
Date: Thu, 20 Aug 2020 15:43:41 +0200	[thread overview]
Message-ID: <20200820134341.GW2674@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtBuZOb9-W5sS=DqxcuMFa8Lw=7XqMJ_YrXEgd5zvufYjA@mail.gmail.com>

> That's been said, not compensating the vruntime for a sched_idle task
> makes sense for me. Even if that will only help for others task in the
> same cfs_rq

Yeah, but it is worth the extra pointer chasing and branches?

Then again, I suppose we started all that with the idle_h_nr_running
nonsense :/

  reply	other threads:[~2020-08-20 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 12:00 [PATCH] sched/fair: avoid vruntime compensation for SCHED_IDLE task Jiang Biao
2020-08-20 12:51 ` Vincent Guittot
2020-08-20 12:58   ` peterz
2020-08-20 13:15     ` Vincent Guittot
2020-08-20 13:43       ` peterz [this message]
2020-08-20 14:09         ` Vincent Guittot
2020-08-20 14:24           ` Jiang Biao
2020-08-23  7:33           ` Jiang Biao
2020-08-28 12:55             ` Vincent Guittot
2020-09-01 10:14               ` Jiang Biao
2020-09-01 13:04                 ` Vincent Guittot
2020-09-01 14:19                   ` Jiang Biao
2020-08-20 14:19     ` Jiang Biao
2020-08-20 14:15   ` Jiang Biao
2020-08-21  0:37 ` [sched/fair] 88d13f778f: WARNING:at_kernel/sched/fair.c:#place_entity kernel test robot

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=20200820134341.GW2674@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=benbjiang@gmail.com \
    --cc=benbjiang@tencent.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