| commit | a8728944efe23417e38bf22063f06d9d8ee21d59 | [log] [tgz] |
|---|---|---|
| author | Gregory Haskins <ghaskins@novell.com> | Mon Dec 29 09:39:49 2008 -0500 |
| committer | Gregory Haskins <ghaskins@novell.com> | Mon Dec 29 09:39:49 2008 -0500 |
| tree | 225f453912a50a4baf0fdbc578c31bd23d4780f6 | |
| parent | e864c499d9e57805ae1f9e7ea404dd223759cd53 [diff] |
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>