From: Gregory Haskins <ghaskins@novell.com>
Date: Mon, 29 Dec 2008 14:39:49 +0000 (-0500)
Subject: sched: use highest_prio.curr for pull threshold
X-Git-Tag: v2.6.30-rc1~658^2~24^2~3^2~8
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a8728944efe23417e38bf22063f06d9d8ee21d59;p=pandora-kernel.git

sched: use highest_prio.curr for pull threshold

highest_prio.curr is actually a more accurate way to keep track of
the pull_rt_task() threshold since it is always up to date, even
if the "next" task migrates during double_lock.  Therefore, stop
looking at the "next" task object and simply use the highest_prio.curr.

Signed-off-by: Gregory Haskins <ghaskins@novell.com>
---

Reading git-diff-tree failed