From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: high resolution timers and timer interrupt thrashing
Date: Tue, 13 May 2014 10:09:30 +0800 [thread overview]
Message-ID: <53717EDA.9000204@gmail.com> (raw)
In-Reply-To: <CAP0SO-EOaQUXxMmgCUJoJpPW7t1i-+VJ3DgNhDQgbcyQeX2Ygw@mail.gmail.com>
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
next prev parent reply other threads:[~2014-05-13 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 17:55 high resolution timers and timer interrupt thrashing Sudharsan Vijayaraghavan
2014-05-13 2:09 ` bill4carson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 6:00 Sudharsan vijayaraghavan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53717EDA.9000204@gmail.com \
--to=bill4carson@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).