kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: vikram186@gmail.com (Vikram Narayanan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Enabling tickless kernel feature in ARM
Date: Wed, 27 Apr 2011 08:39:58 +0530	[thread overview]
Message-ID: <BANLkTikfUvnrb9AhwiVfJ3vo7NfhBJQz5Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinyb+_wpPWVgtdRwYT8nr3W7fM+ng@mail.gmail.com>

Dear,

On Tue, Apr 26, 2011 at 10:05 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Dear Vikram...
>
> On Tue, Apr 26, 2011 at 20:55, Vikram Narayanan <vikram186@gmail.com> wrote:
>> Hi,
>>
>> I want to enable the dynamic tick aka tickless kernel feature for the
>> BSP which I am developing. What are all the architecture dependent
>> changes that needs to be done for implementing it.
>
> To the best I know:
>
> essentially, to achieve tickless ( also know as "no hz"), you need to
> reprogram your timer chip, so it just "shoot" whenever needed, not
> periodically. And sometimes, you need to round them up, i.e there are
> timers which expires in the next 10 ms, 11 ms and 15 ms...so
> effectively, better to make them expire at 15 ms if possible.
>
> so, you need a way to detect the timer expiration (possibly by walking
> through active timer list) and decide when the timer chip needs to
> shoot interrupt. The rest of the change...of course...still needed
> further thinking....
>
> NB: AFAIK In x86, HPET is a prerequisite to achieve tickless... maybe
> because reprogramming HPET is somewhat way faster than regular PIT
I have read about the dynamic tick feature in lwn.net. When I see the
source, it seems to have implemented only with the HPET timers. and
also, these dynamic ticks are achieved with hrtimers nowadays.
http://lxr.linux.no/#linux+v2.6.38/Documentation/timers/highres.txt#L204
Also I believe most of the implementation is moved to the arch
independent part with the help of clocksource and clockevents.
Do I need to enable hrtimers for enabling the dynamic tick feature.?

-
Thanks
Vikram
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>

  reply	other threads:[~2011-04-27  3:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 13:55 Enabling tickless kernel feature in ARM Vikram Narayanan
2011-04-26 16:34 ` Haojian Zhuang
2011-04-27  3:04   ` Vikram Narayanan
2011-04-27  6:29     ` Haojian Zhuang
2011-04-26 16:35 ` Mulyadi Santosa
2011-04-27  3:09   ` Vikram Narayanan [this message]
2011-04-27  4:29     ` Mulyadi Santosa
2011-04-27 13:49       ` Vikram Narayanan
2011-04-27 15:37         ` Mulyadi Santosa
2011-04-28 13:18           ` Vikram Narayanan
2011-04-28 15:08             ` Mulyadi Santosa
2011-04-28 16:20               ` Vikram Narayanan

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=BANLkTikfUvnrb9AhwiVfJ3vo7NfhBJQz5Q@mail.gmail.com \
    --to=vikram186@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).