From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: HZ in 2.6 on PPC32
Date: Sat, 23 Aug 2003 18:59:54 +0200 [thread overview]
Message-ID: <1061657994.772.6.camel@gaston> (raw)
In-Reply-To: <1061654591.1251.34.camel@thor.holligenstrasse29.lan>
On Sat, 2003-08-23 at 18:03, Michel Dänzer wrote:
> Why is this still defined to 100? I'm running at 1000 now, and it makes
> a huge difference for interactivity. Moreover, CONFIG_PREEMPT now makes
> things even better instead of worse. :)
>
> If the reason is the slow PPC32 CPUs still around, maybe make it a
> config option?
A config option would probably be a better idea, I doubt lots of embedded
or low end configs wants HZ at 1000... Regarding CONFIG_PREEMPT, it's
really weird that it "makes things worse" for you with HZ at 100. But
that may also be the 2.6-test scheduler suckyness...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-23 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 16:03 HZ in 2.6 on PPC32 Michel Dänzer
2003-08-23 16:59 ` Benjamin Herrenschmidt [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=1061657994.772.6.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
/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).