[lkml]   [1999]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: lowlatency-2.2.13-A1 questions

I think I figured out what is happening with the scheduling latency
problem I reported earlier.

An interrupt can occur during the kernel schedule function
just prior to the "__switch_to" function and the interrupt handler
may add a new task to the run-queue and set current->need_resched.
Then the current task gets switched out immediately and the need_resched
flag is lost. Should the new task inherit need_resched in this
case? Is this an oversight or is this intentional?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:55    [W:0.040 / U:165.364 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site