diff options
author | 2008-12-29 09:39:49 -0500 | |
---|---|---|
committer | 2008-12-29 09:39:49 -0500 | |
commit | a8728944efe23417e38bf22063f06d9d8ee21d59 (patch) | |
tree | 225f453912a50a4baf0fdbc578c31bd23d4780f6 /include/linux/init_task.h | |
parent | sched: track the next-highest priority on each runqueue (diff) | |
download | linux-dev-a8728944efe23417e38bf22063f06d9d8ee21d59.tar.xz linux-dev-a8728944efe23417e38bf22063f06d9d8ee21d59.zip |
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>
Diffstat (limited to 'include/linux/init_task.h')
0 files changed, 0 insertions, 0 deletions