From: Shivdas Gujare <shivdas.tech@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Confused with CONFIG_NO_HZ and CONFIG_HZ
Date: Wed, 20 May 2009 18:16:56 -0700 [thread overview]
Message-ID: <cf70f0210905201816g51d5d99ft35e8f33e2c470f5e@mail.gmail.com> (raw)
Hi all,
I am confused with CONFIG_NO_HZ and CONFIG_HZ? What is the main
difference between it?
As per what I understood, CONFIG_NO_HZ is feature of tickless kernel,
where timer interrupts will be fired only if necessary,
and CONFIG_HZ decides the timeout of timer interrupts?
I came across description[1] from Ingo regarding CONFIG_NO_HZ as "if
there is no timer to be expired for say 1.5 seconds when
the system goes idle, then the system will stay totally idle for 1.5
seconds." then I don't understand how timer will remain unexpired
during idle if CONFIG_HZ=100,
i.e. 10ms timer timeout for timer interrupt and during such scenarios
who decides this 1.5 sec timeout.
It will be great help, if I get some more information regarding this.
Ref.
[1] http://kerneltrap.org/node/6750
Thanks and regards,
Shivdas Gujare
reply other threads:[~2009-05-21 1:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cf70f0210905201816g51d5d99ft35e8f33e2c470f5e@mail.gmail.com \
--to=shivdas.tech@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®