1
0
Files
linux/kernel
Gregory Haskins a8728944ef 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>
2008-12-29 09:39:49 -05:00
..
2008-12-13 21:55:51 +10:30
2008-12-13 21:55:51 +10:30
2008-10-16 11:21:30 -07:00
2008-12-12 13:48:57 +01:00
2008-09-14 16:25:35 +02:00
2008-11-19 18:49:58 -08:00
2008-07-28 14:37:38 +02:00
2008-12-10 08:01:54 -08:00
2008-08-13 12:55:10 +02:00
2008-10-20 15:43:10 +02:00
2008-12-01 19:55:24 -08:00
2008-09-02 19:21:40 -07:00
2008-12-13 21:55:51 +10:30
2008-11-30 11:00:15 -08:00
2008-10-21 15:59:53 +02:00
2008-11-05 10:30:14 +01:00
2008-12-13 21:55:51 +10:30
2008-11-06 08:41:56 +01:00
2008-11-19 18:49:57 -08:00
2008-07-25 10:53:45 -07:00
2008-10-16 11:21:47 -07:00
2008-10-16 11:21:31 -07:00