public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/3] [GIT PULL] sched: clean ups and a minor fix
Date: Wed, 13 Feb 2013 09:33:14 +0100	[thread overview]
Message-ID: <20130213083314.GA7149@gmail.com> (raw)
In-Reply-To: <20130212225412.781044738@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> Ingo,
> 
> The first of the patches is a minor fix to when a woken RT task is about
> to preempt a pinned RT task, push_rt_task() is called to try to
> migrate the woken task if possible (to avoid preempting a pinned RT
> task that may be the second highest priority task in the system).
> 
> But the issue is that push_rt_task() won't push it if the woken task
> is higher priority even if the task to be preempted is pinned.
> 
> The second two patches is more of a clean up to remove the idle
> hooks in the scheduler proper, and to use the pre/post schedule
> methods instead.
> 
> This allows interrupts to be enabled in the idle balance, which slightly
> helps latencies, especially for the -rt kernel. Other patches can be
> added on top. Maybe in the future preemption could be enabled during
> the idle balance as well. But that remains to be seen.
> 
> Please pull the latest tip/sched/core tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/sched/core
> 
> Head SHA1: 1db13ecf89054d39922e7b3323d124c7e2921560
> 
> 
> Steven Rostedt (Red Hat) (3):
>       sched/rt: Fix push_rt_task() to have the same checks as the caller did
>       sched: Move idle_balance() to post_schedule
>       sched: Enable interrupts in idle_balance()
> 
> ----
>  kernel/sched/core.c      |    3 ---
>  kernel/sched/fair.c      |    8 +++++---
>  kernel/sched/idle_task.c |   10 ++++++++++
>  kernel/sched/rt.c        |   15 ++++++++++-----
>  4 files changed, 25 insertions(+), 11 deletions(-)

Pulled, thanks a lot Steve!

	Ingo

      parent reply	other threads:[~2013-02-13  8:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 22:54 [PATCH 0/3] [GIT PULL] sched: clean ups and a minor fix Steven Rostedt
2013-02-12 22:54 ` [PATCH 1/3] sched/rt: Fix push_rt_task() to have the same checks as the caller did Steven Rostedt
2013-02-12 22:54 ` [PATCH 2/3] sched: Move idle_balance() to post_schedule Steven Rostedt
2013-02-13 18:43   ` Peter Zijlstra
2013-02-13 19:05     ` Steven Rostedt
2013-02-15 11:51       ` Peter Zijlstra
2013-02-15 13:37         ` Steven Rostedt
2013-02-14 14:25     ` Steven Rostedt
2013-02-12 22:54 ` [PATCH 3/3] sched: Enable interrupts in idle_balance() Steven Rostedt
2013-02-13  8:33 ` Ingo Molnar [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=20130213083314.GA7149@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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