[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081204154100.21712.88806.stgit@dev.haskins.net>
Date: Thu, 04 Dec 2008 10:43:36 -0500
From: Gregory Haskins <ghaskins@...ell.com>
To: mingo@...e.hu
Cc: peterz@...radead.org, rostedt@...dmis.org, ghaskins@...ell.com,
linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: [PATCH v3 0/4] sched: track next-highest priority
Hi Ingo,
Here is the updated series, per my note about the bug in v2 last night.
Changes since v2
Fix bug in 2/4 related to recomputing .next in dec_rt_task()
-Greg
---
Gregory Haskins (4):
sched: use highest_prio.next to optimize pull operations
sched: use highest_prio.curr for pull threshold
sched: track the next-highest priority on each runqueue
sched: cleanup inc/dec_rt_tasks
kernel/sched.c | 8 ++-
kernel/sched_rt.c | 156 +++++++++++++++++++++++++++++++----------------------
2 files changed, 98 insertions(+), 66 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists