From: Stas Sergeev <stsp@aknet.ru>
To: Lee Revell <rlrevell@joe-job.com>
Cc: john stultz <johnstul@us.ibm.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] API for timer hooks
Date: Wed, 17 Aug 2005 21:41:12 +0400 [thread overview]
Message-ID: <430376B8.9040404@aknet.ru> (raw)
In-Reply-To: <1124296844.3591.7.camel@mindpipe>
Hello.
Lee Revell wrote:
> Lots of things aren't doable with the current timer API, hence all the
> recent work on dynamic tick.
I've found only this about the dynamic
tick:
http://lwn.net/Articles/138969/
and it seems that it is intended only
to slow down the interrupts when there
is no work to do, rather than to allow
setting an arbitrary frequencies or something
like that.
I guess now I realized how you (and Nish)
assume I could use it: is it that I
should set CONFIG_HZ to the value I
need at compile-time, and just remove
all the timer reprogramming from the
driver in a hope the dynamic-tick patch
will slow it down itself when necessary?
Or am I misunderstanding the suggestion?
That would be really excellent, but
it there a patch around that allows to
set an arbitrary CONFIG_HZ values, or should
I try to code up one myself? I think
I tried that a few years ago, and the
code all around the kernel was resisting
to work with HZ>1000, but I guess now
it was all changed.
next prev parent reply other threads:[~2005-08-17 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 13:36 [rfc][patch] API for timer hooks Stas Sergeev
2005-08-15 17:19 ` john stultz
2005-08-16 20:21 ` Stas Sergeev
2005-08-16 22:24 ` Nish Aravamudan
2005-08-17 16:10 ` Stas Sergeev
2005-08-17 2:09 ` Lee Revell
2005-08-17 16:21 ` Stas Sergeev
2005-08-17 16:40 ` Lee Revell
2005-08-17 17:41 ` Stas Sergeev [this message]
2005-08-17 23:16 ` Lee Revell
2005-08-18 16:59 ` Stas Sergeev
2005-08-18 17:07 ` Lee Revell
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=430376B8.9040404@aknet.ru \
--to=stsp@aknet.ru \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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