From: Segher Boessenkool <segher@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, Kumar Gala <galak@freescale.com>
Subject: Re: [PATCH] ppc32: add CONFIG_HZ
Date: Mon, 29 Aug 2005 17:31:20 +0200 [thread overview]
Message-ID: <873573479a451f5b7ac63763237a1c27@kernel.crashing.org> (raw)
In-Reply-To: <f0351d402e64b569bbcfc16fa921d860@embeddededge.com>
>> 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? :-)
Sure. And some people are actually working on that. But
on common x86 hardware, it seems to be a really really hard
thing to do. Would be a lot easier in PowerPC of course...
Segher
next prev parent reply other threads:[~2005-08-29 15:30 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
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 [this message]
-- 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=873573479a451f5b7ac63763237a1c27@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=dan@embeddededge.com \
--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).