From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Robert Bradbury <robert.bradbury@gmail.com>
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: Broken ondemand scheduler in Linux 2.6.30+ on Pentium IVs
Date: Mon, 26 Oct 2009 18:23:04 +0000 [thread overview]
Message-ID: <20091026182304.GB4657@srcf.ucam.org> (raw)
In-Reply-To: <deaa866a0910251546m7ea001bcm252c41e65927a424@mail.gmail.com>
...except that conservative has the same latency threshold as ondemand,
which I'm sure wasn't supposed to be the case. I've added the cpufreq
list to Cc:.
(Summary: p4-clockmod had its latency changed to avoid ondemand using
it, which was done to avoid the performance impact that ondemand
generates on p4s. I thought that conservative was still supposed to work
here, but as it has the same latency threshold it doesn't)
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-10-26 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 22:46 Broken ondemand scheduler in Linux 2.6.30+ on Pentium IVs Robert Bradbury
[not found] ` <20091026015755.7482.qmail@stuge.se>
2009-10-26 11:50 ` Robert Bradbury
2009-10-26 18:19 ` Matthew Garrett
2009-10-26 18:23 ` Matthew Garrett [this message]
2009-10-27 0:44 ` Robert Hancock
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=20091026182304.GB4657@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.bradbury@gmail.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