Re: Current Best Practices for periodic threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On a somewhat related topic... how do folks stagger the startup of
> periodic threads?  For example, suppose one (high priority) thread
> needs to run every 20ms, only takes 1ms to do its work, but _really_
> needs to run on that 20ms clock.  Now suppose some other thread needs
> 4ms out of every 20ms to accomplish it's work.  If it were to start
> 9ms after the first thread started, then every 10ms one thread or the
> other would run, leaving 15ms for non-realtime (or lower priority real
> time) threads to run.
>
> I can imagine any number of home-grown solutions to manage the
> staggered startup of these two threads.  I am wondering if there is a
> more standard way to do this.

Can we simply configure the "timer slack" appropriately and
let the kernel decide how much to stagger or coalesce
the timer events as it sees fit?
https://lwn.net/Articles/369361/


regards
CVS
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux