On Mon, 12 Sep 2005 11:01:15 +0200
Ingo Molnar <[email protected]> wrote:
> > 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.
Ah,
thanks for the info. So it is a user (me) bug in the end :) This has
helped. Actually the code i had attached had another bug in it. But that
wasn't the responsible one.
Thanks again, and sorry for the multiple mails,
Florian Schmidt
--
Palimm Palimm!
http://tapas.affenbande.org
-
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]
| |
 |