On Thu, Apr 28, 2011 at 8:38 PM, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
On 28/04/2011, Vikram Narayanan <vikram186@gmail.com> wrote:
I am planning to have a tick of 10ms. i.e the HZ value as 100. Will that be good enough?
Sorry, you misunderstood me. What I meant was "how long it takes to reprogram the timer, so it ready to deliver another interupt". This is based on my rough info that some timers are quick to be reprogrammed, some are slow...the rest are damn slow. And since we deal with uncertainty (timers could be needed at any point), the fastest one is the best bet.
Hopefully I explain it clearly now... Yeah. Actually I didn't measure the timer reprogramming latency yet. But I think it will be quite good. My assumption may go wrong. Are there any other considerations to take care while implementing the clocksource/clockevents?
Thanks, Vikram
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com