linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH 0/7] sched: various updates to the scheduler
Date: Thu, 16 Jun 2011 22:40:33 -0400	[thread overview]
Message-ID: <1308278433.9218.163.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110617015516.301117218@goodmis.org>

On Thu, 2011-06-16 at 21:55 -0400, Steven Rostedt wrote:
> Peter,
> 
> Can you review these patches and give your Acked-by, or explain what
> might be wrong with them. No hurry, I haven't pushed them through my
> full testing yet (starting that now). But I want to push them out for
> 3.1.
> 
> Thanks,
> 
> -- Steve
> 
> 
> This patch set can be found in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-rt.git
> tip/sched/core
> 
> Head SHA1: cac554411989613131d899cfb51b622ce96d5136
> 
> 
> Hillf Danton (5):
>       sched: Fix need_resched() when checking peempt

You don't need to review this one. I just realized that I pushed that
already for 3.0 pull.

Thanks!

-- Steve



>       sched: Remove noop in next_prio()
>       sched: Remove noop in lowest_flag_domain()
>       sched, rt: Fix rq->rt.pushable_tasks bug in push_rt_task()
>       sched: Remove resetting exec_start in put_prev_task_rt()
> 
> Steven Rostedt (2):
>       sched: Balance RT tasks when forked as well
>       sched: Use pushable_tasks to determine next highest prio
> 
> ----
>  kernel/sched_fair.c |    2 +-
>  kernel/sched_rt.c   |   88 +++++++++++++++++++--------------------------------
>  2 files changed, 34 insertions(+), 56 deletions(-)



      parent reply	other threads:[~2011-06-17  2:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17  1:55 [RFC][PATCH 0/7] sched: various updates to the scheduler Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 1/7] sched: Fix need_resched() when checking peempt Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 2/7] sched: Remove noop in next_prio() Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 3/7] sched: Remove noop in lowest_flag_domain() Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 4/7] sched, rt: Fix rq->rt.pushable_tasks bug in push_rt_task() Steven Rostedt
2011-06-17  2:33   ` Mike Galbraith
2011-06-17  2:41     ` Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 5/7] sched: Remove resetting exec_start in put_prev_task_rt() Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 6/7] sched: Balance RT tasks when forked as well Steven Rostedt
2011-07-26 12:25   ` Peter Zijlstra
2011-07-26 12:35     ` Steven Rostedt
2011-07-26 12:36       ` Peter Zijlstra
2011-07-26 12:50         ` Steven Rostedt
2011-08-14 16:05   ` [tip:sched/core] " tip-bot for Steven Rostedt
2011-06-17  1:55 ` [RFC][PATCH 7/7] sched: Use pushable_tasks to determine next highest prio Steven Rostedt
2011-06-17  2:40 ` Steven Rostedt [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=1308278433.9218.163.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).