mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [GIT PULL] scheduler updates for v4.15
Date: Mon, 13 Nov 2017 10:23:35 +0100	[thread overview]
Message-ID: <1510565015.15042.38.camel@gmx.de> (raw)
In-Reply-To: <20171113080054.hvpfoo6bd7ae2yu4@gmail.com>

On Mon, 2017-11-13 at 09:00 +0100, Ingo Molnar wrote:
> 
>  - Improve the RT IPI based balancing logic (Steven Rostedt)

Well how 'bout that, serendipity strikes again:

I just got a report that a proggy Gregory Haskins wrote back in 2007
(preempt-test) was claiming RT was broken, but no, it's every kernel
containing b6366f048e0c.  What the proggy does is to start a gaggle of
RT tasks of descending priority, giving each an identical quantum of
work to do, expecting higher priority tasks to get it done before
lower.  That currently does not always happen, we occasionally do not
get a task pushed for long enough that a task that should have been
preempted by a push shortly after hitting the CPU, manages to remain
long enough to finish well before it should have been able to.

This patch fixed it up before I could even get my troubleshooting
wheels properly smoking (they spin a bit before getting traction).
 Given that, not to mention b6366f048e0c being capable of log jamming
even fairly modest boxen, perhaps this patch wants a stable tag?

	-Mike

  reply	other threads:[~2017-11-13  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13  8:00 Ingo Molnar
2017-11-13  9:23 ` Mike Galbraith [this message]
2017-11-13 15:13   ` Ingo Molnar

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=1510565015.15042.38.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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®