* high resolution timers and timer interrupt thrashing
@ 2014-04-20 17:55 Sudharsan Vijayaraghavan
2014-05-13 2:09 ` bill4carson
0 siblings, 1 reply; 3+ messages in thread
From: Sudharsan Vijayaraghavan @ 2014-04-20 17:55 UTC (permalink / raw)
To: kernelnewbies
Hi All,
With CONFIG_HIGH_RES_TIMERS configured and a whole lot of timer_create with
interval of less than jiffy (i.e., few nano seconds) we are bound to
get timer interrupts
less than a jiffy because set_next_event will configure for expires
less than jiffy.
This means we are thrashing the system with more timer interrupts,
perhaps to extent
of almost every clock tick, is my understanding correct?
Given this is it not dangerous to configure CONFIG_HIGH_RES_TIMERS
Please give your thoughts
Thanks,
Sudharsan
^ permalink raw reply [flat|nested] 3+ messages in thread
* high resolution timers and timer interrupt thrashing
@ 2014-04-21 6:00 Sudharsan vijayaraghavan
0 siblings, 0 replies; 3+ messages in thread
From: Sudharsan vijayaraghavan @ 2014-04-21 6:00 UTC (permalink / raw)
To: kernelnewbies
Hi All,
With CONFIG_HIGH_RES_TIMERS configured and a whole lot of timer_create with
interval of less than jiffy (i.e., few nano seconds) we are bound to
get timer interrupts
less than a jiffy because set_next_event will configure for expires
less than jiffy.
This means we are thrashing the system with more timer interrupts,
perhaps to extent
of almost every clock tick, is my understanding correct?
Given this is it not dangerous to configure CONFIG_HIGH_RES_TIMERS
Please give your thoughts
Thanks,
Sudharsan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140421/b4aeee54/attachment-0001.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* high resolution timers and timer interrupt thrashing
2014-04-20 17:55 high resolution timers and timer interrupt thrashing Sudharsan Vijayaraghavan
@ 2014-05-13 2:09 ` bill4carson
0 siblings, 0 replies; 3+ messages in thread
From: bill4carson @ 2014-05-13 2:09 UTC (permalink / raw)
To: kernelnewbies
On 2014?04?21? 01:54, Sudharsan Vijayaraghavan wrote:
> Hi All,
>
> With CONFIG_HIGH_RES_TIMERS configured and a whole lot of timer_create with
> interval of less than jiffy (i.e., few nano seconds) we are bound to
> get timer interrupts
> less than a jiffy because set_next_event will configure for expires
> less than jiffy.
>
> This means we are thrashing the system with more timer interrupts,
> perhaps to extent
> of almost every clock tick, is my understanding correct?
Yes, with hrtimer enabled, timer interrupt could be more frequently ever than before.
The effort of hrtimer is to enable high resolution timing for user land application
like video/audio like wise.
You can google why hrtimer was made to solve what kind of problem.
> Given this is it not dangerous to configure CONFIG_HIGH_RES_TIMERS
> Please give your thoughts
>
> Thanks,
> Sudharsan
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
?????????,??????????
--bill
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-13 2:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-20 17:55 high resolution timers and timer interrupt thrashing Sudharsan Vijayaraghavan
2014-05-13 2:09 ` bill4carson
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 6:00 Sudharsan vijayaraghavan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).