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: Thu, 28 Apr 2011 21:50:35 +0530	[thread overview]
Message-ID: <BANLkTikPpbw34-FYF+vUwrUREmDx7mFihQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikUY+wyUvKsTmR5aEL2DowJjiWP8Q@mail.gmail.com>

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
>

      reply	other threads:[~2011-04-28 16:20 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
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 [this message]

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=BANLkTikPpbw34-FYF+vUwrUREmDx7mFihQ@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).