All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: William Heimbigner <icxcnika@mar.tar.cc>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] [PATCH] cpufreq: allow full selection of default governors
Date: Tue, 24 Apr 2007 20:03:27 -0400	[thread overview]
Message-ID: <20070425000327.GG22267@redhat.com> (raw)
In-Reply-To: <29495f1d0704241505p62140160o52d83e383106bf8e@mail.gmail.com>

On Tue, Apr 24, 2007 at 03:05:36PM -0700, Nish Aravamudan wrote:
 > On 4/24/07, Dave Jones <davej@redhat.com> wrote:
 > > On Tue, Apr 24, 2007 at 09:03:23PM +0000, William Heimbigner wrote:
 > >  > The following patches should allow selection of conservative, powersave, and
 > >  > ondemand in the kernel configuration.
 > >
 > > This has been rejected several times already.
 > > Ondemand and conservative isn't a viable governor for all cpufreq
 > > implementations (ie, ones with high switching latencies).
 > 
 > This piques my curiosity -- some governors don't work with some
 > cpufreq implementations. Are those implementations in the kernel or in
 > userspace? If in the kernel, then perhaps there should be some
 > dependency expressed there in Kconfig between cpufreq implementation
 > and the available governors

it can't be solved that easily. powernow-k8 for example is fine to
use with ondemand on newer systems, where the latency is low.
On older models however, it isn't.

 > > Also, see the
 > > comment in the Kconfig a few lines above where you are adding this.
 > 
 > Are these governors unfixable? If

tbh, I've forgotten the original issues that caused the comment
to be placed there. Dominik ?

 > Just looking for more info -- feel free to just point me at the archives.

cpufreq-list archives are at http://lists.linux.org.uk/mailman/listinfo/cpufreq
(though only available to list members)

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-04-25  0:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 21:03 [RFC] [PATCH] cpufreq: allow full selection of default governors William Heimbigner
2007-04-24 21:12 ` Dave Jones
2007-04-24 21:25   ` Chuck Ebbert
2007-04-24 22:05   ` Nish Aravamudan
2007-04-25  0:03     ` Dave Jones [this message]
2007-04-27  1:54       ` Dominik Brodowski
2007-04-27  6:09         ` Dave Jones
2007-04-27 12:24           ` Dominik Brodowski
2007-04-27 13:40             ` William Heimbigner
2007-04-27 17:06             ` Gautham Shenoy
2007-04-27 18:17               ` William Heimbigner
2007-04-24 22:35   ` William Heimbigner
2007-04-24 21:13 ` Robert P. J. Day

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=20070425000327.GG22267@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=icxcnika@mar.tar.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nish.aravamudan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.