sched: use highest_prio.curr for pull threshold

Browse source

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>

...

This commit is contained in:

Gregory Haskins 2008-12-29 09:39:49 -05:00

parent e864c499d9

commit a8728944ef

1 changed files with 6 additions and 25 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

31

kernel/sched_rt.c

View file