From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] RT scheduler updates for tip
Date: Mon, 8 Dec 2008 15:32:28 +0100 [thread overview]
Message-ID: <20081208143228.GF14856@elte.hu> (raw)
In-Reply-To: <493939B1.40506@novell.com>
* Gregory Haskins <ghaskins@novell.com> wrote:
> Hi Ingo,
> FWIW, I have placed all my latest upstream-able scheduler patches into
> a branch in my git tree (against tip/master).
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ghaskins/linux-2.6-hacks.git
> sched/latest
>
> Gregory Haskins (11):
> sched: cleanup inc/dec_rt_tasks
> sched: track the next-highest priority on each runqueue
> sched: use highest_prio.curr for pull threshold
> sched: use highest_prio.next to optimize pull operations
> sched: only try to push a task on wakeup if it is migratable
> sched: pull only one task during NEWIDLE balancing to limit
> critical section
> sched: make double-lock-balance fair
> sched: add sched_class->needs_post_schedule() member
> plist: fix PLIST_NODE_INIT to work with debug enabled
> sched: create "pushable_tasks" list to limit pushing to one attempt
> RT: fix push_rt_task() to handle dequeue_pushable properly
>
> include/linux/init_task.h | 1 +
> include/linux/plist.h | 9 +-
> include/linux/sched.h | 2 +
> kernel/sched.c | 89 +++++++++++--
> kernel/sched_rt.c | 324
> +++++++++++++++++++++++++++++++--------------
> 5 files changed, 312 insertions(+), 113 deletions(-)
>
> These are built/booted on my quad-core/x86_64 and look good to me.
>
> 1) the first four are the "next-highest" v3 patches that I submitted
> yesterday 2) the last seven are patches that Steven has carried in
> 26-rt that have not yet been pulled in to tip
>
> I assume there is an implicit ACK from Steven on (2) since he pulled
> them into -rt. We still await comment from Peter re: (1).
pulled into tip/cpus4096, thanks Gregory!
(It goes into the cpumask tree because it already changed a few areas
that you relied on.)
Ingo
next prev parent reply other threads:[~2008-12-08 14:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:24 [git pull] RT scheduler updates for tip Gregory Haskins
2008-12-08 14:32 ` Ingo Molnar [this message]
2008-12-08 16:05 ` [PATCH] sched: fix build failure in kernel/sched_rt.c Ingo Molnar
2008-12-08 16:14 ` Gregory Haskins
2008-12-08 16:12 ` [git pull] RT scheduler updates for tip Ingo Molnar
2008-12-08 16:57 ` Gregory Haskins
2008-12-09 14:35 ` Gregory Haskins
2008-12-12 11:34 ` Ingo Molnar
2008-12-12 11:49 ` Ingo Molnar
2008-12-29 15:37 ` Gregory Haskins
2008-12-29 18:13 ` Gregory Haskins
2009-01-11 4:01 ` Ingo Molnar
2009-01-11 9:53 ` Ingo Molnar
2009-01-12 14:45 ` Gregory Haskins
2009-01-12 14:45 ` Ingo Molnar
2009-01-12 15:05 ` Gregory Haskins
2009-01-12 19:23 ` [git pull] fixes for tip/sched/rt Gregory Haskins
2009-01-13 1:43 ` Ingo Molnar
2009-01-13 2:37 ` [PATCH v2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-14 8:01 ` Ingo Molnar
2009-01-14 10:54 ` Peter Zijlstra
2009-01-14 11:03 ` Ingo Molnar
2009-01-14 13:21 ` Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 0/2] fixes for tip/sched/rt Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 1/2] sched: de CPP-ify the scheduler code Gregory Haskins
2009-01-14 15:11 ` Steven Rostedt
2009-01-14 15:28 ` Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 2/2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-15 12:30 ` [PATCH v3 0/2] fixes for tip/sched/rt Ingo Molnar
2009-01-16 13:35 ` Ingo Molnar
2009-01-16 13:45 ` Gregory Haskins
2009-01-16 13:46 ` Peter Zijlstra
2009-01-16 14:02 ` Gregory Haskins
2009-01-16 14:02 ` 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=20081208143228.GF14856@elte.hu \
--to=mingo@elte.hu \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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