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

sched: use highest_prio.next to optimize pull operations

We currently take the rq->lock for every cpu in an overload state during
pull_rt_tasks().  However, we now have enough information via the
highest_prio.[curr|next] fields to determine if there is any tasks of
interest to warrant the overhead of the rq->lock, before we actually take
it.  So we use this information to reduce lock contention during the
pull for the case where the source-rq doesnt have tasks that preempt
the current task.

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

Reading git-diff-tree failed