* Florian Schmidt <[email protected]> wrote:
> Problem is: i wrote a small test program running at prio 80 that
> simply busy loops for about 15 seconds. It seems from the log output
> that the main thread never wakes up during the time of the test
> program running.
>
> Sep 12 10:36:07 mango rt_watchdog: count 5
> Sep 12 10:36:30 mango rt_watchdog: count 6
> ^^
> 23 seconds gap between two wakeups
>
> Maybe my understanding of how sched fifo works is wrong, but i assumed
> a higher prio thread shold get woken up from a sleep by the scheduler
> which gets run by the timer interrupt [which is still non
> preemptible].
depending on what type of timeout you are using you'll also need to chrt
the softirq-timer kernel thread(s) to prio 99. Otherwise the timer fn
will have no chance to be executed. There's work going on by Thomas to
make such things automatic, by prioritizing timers. If you have HRT
enabled in the .config then it should mostly be automatic already
though.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|