Re: lowlatency-2.2.13-A1 questions

William Montgomery (william@opinicus.com)
Thu, 2 Dec 1999 14:01:10 -0500 (EST)


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?

Wm

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/