From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <galak@freescale.com>
Cc: Andrew Morton <akpm@osdl.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc32: add CONFIG_HZ
Date: Fri, 26 Aug 2005 16:13:04 -0400 [thread overview]
Message-ID: <f0351d402e64b569bbcfc16fa921d860@embeddededge.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508261415080.29975@nylon.am.freescale.net>
On Aug 26, 2005, at 3:15 PM, Kumar Gala wrote:
> While ppc32 has the CONFIG_HZ Kconfig option, it wasnt actually being
> used. Connect it up and set all platforms to 250Hz. This pretty much
> mimics the ppc64 patch from Anton Blanchard.
Why do we keep cranking up this clock frequency? Do we really need
it running that fast? Is it time for someone with RTOS experience to
implement a real scheduled clock queue in Linux instead of just
wasting interrupts decrementing a counter waiting for the next
event to expire? :-) If the user "ticks" are still 100 Hz, don't we
need
something that is an integer multiple of that for at least an attempt
at getting it close to what a user would request?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-08-26 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 19:15 [PATCH] ppc32: add CONFIG_HZ Kumar Gala
2005-08-26 20:13 ` Dan Malek [this message]
2005-08-26 21:31 ` Tom Rini
2005-08-26 22:52 ` Dan Malek
2005-09-08 1:04 ` Marcelo Tosatti
2005-09-08 14:11 ` Kumar Gala
2005-09-08 15:53 ` Dan Malek
2005-08-29 15:31 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 22:48 Rune Torgersen
2005-08-26 22:54 ` Dan Malek
2005-08-26 22:55 ` Tom Rini
2005-08-26 23:07 ` Dan Malek
2005-08-26 23:13 ` Tom Rini
2005-08-27 5:04 ` Grant Likely
2005-08-28 0:48 ` Dan Malek
2005-08-28 2:19 ` Paul Mackerras
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=f0351d402e64b569bbcfc16fa921d860@embeddededge.com \
--to=dan@embeddededge.com \
--cc=akpm@osdl.org \
--cc=galak@freescale.com \
--cc=linuxppc-dev@ozlabs.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).