Fix up 'need_resched()' definition
authorLinus Torvalds <torvalds@linux-foundation.org>
Mon, 12 May 2008 17:14:22 +0000 (10:14 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Mon, 12 May 2008 17:14:22 +0000 (10:14 -0700)
We should not go through the task pointer to get at the thread info,
since it's usually cheaper to just access the thread info directly.

So don't make the code look up 'current', when we can just use the
thread info accessor functions directly.  This generally avoids one
level of indirection and tends to work better together with code that
also looks at other thread flags (eg preempt_count).

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/sched.h

index 4ab9f32f9238a077e0691804daec99463cb225f1..5a63f2d72af6e1e84035bb91df75bd25b843fb6b 100644 (file)
@@ -2027,7 +2027,7 @@ static inline int fatal_signal_pending(struct task_struct *p)
 
 static inline int need_resched(void)
 {
-       return unlikely(test_tsk_need_resched(current));
+       return unlikely(test_thread_flag(TIF_NEED_RESCHED));
 }
 
 /*