public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] sched: Spare IPI on single task renice
Date: Wed, 4 Dec 2019 13:20:54 +0100	[thread overview]
Message-ID: <20191204122054.GS2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191203160106.18806-1-frederic@kernel.org>

On Tue, Dec 03, 2019 at 05:01:04PM +0100, Frederic Weisbecker wrote:
> A couple of patches to avoid disturbing nohz_full CPUs when a single
> fair task get its priority changed. I should probably check other sched
> policies as well...

Yeah, auditing all that sounds like a good idea.

> Frederic Weisbecker (2):
>   sched: Spare resched IPI when prio changes on a single fair task
>   sched: Use fair:prio_changed() instead of ad-hoc implementation

These look good though, thanks!

      parent reply	other threads:[~2019-12-04 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 16:01 [PATCH 0/2] sched: Spare IPI on single task renice Frederic Weisbecker
2019-12-03 16:01 ` [PATCH 1/2] sched: Spare resched IPI when prio changes on a single fair task Frederic Weisbecker
2019-12-17 12:39   ` [tip: sched/core] " tip-bot2 for Frederic Weisbecker
2019-12-03 16:01 ` [PATCH 2/2] sched: Use fair:prio_changed() instead of ad-hoc implementation Frederic Weisbecker
2019-12-17 12:39   ` [tip: sched/core] " tip-bot2 for Frederic Weisbecker
2019-12-04 12:20 ` Peter Zijlstra [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=20191204122054.GS2844@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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