From: Dave Jones <davej@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: ondemand as default governor
Date: Wed, 7 Mar 2007 02:02:08 -0500 [thread overview]
Message-ID: <20070307070208.GB15453@redhat.com> (raw)
In-Reply-To: <200703070124.29058.lenb@kernel.org>
On Wed, Mar 07, 2007 at 01:24:28AM -0500, Len Brown wrote:
> On Thursday 01 March 2007 12:41, Thomas Renninger wrote:
> > I just read in drivers/cpufreq/Kconfig:
> >
> > # Note that it is not currently possible to set the other governors
> > (such as ondemand)
> > # as the default, since if they fail to initialise, cpufreq will be
> > # left in an undefined state.
> >
> > Is this a bigger problem to solve?
> > Is there already someone working/thinking on/about a solution?
> >
> > Allowing this would be convenient...
>
> Yes, it would, then we could delete the other governors,
> and then delete the concept of multiple governors alltogether.
It's not feasible unless you have a way of making various
older CPUs transition faster. Ondemand on longhaul,powernow-k6,longrun,
elanfreq, as well as lots of non-x86 implementations is just not
a feasible option.
However.. conservative might be. I'd still like to see conservative
folded into ondemand sometime, and just be a module param.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-07 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:41 ondemand as default governor Thomas Renninger
2007-03-07 6:24 ` Len Brown
2007-03-07 7:02 ` Dave Jones [this message]
2007-03-07 9:20 ` Thomas Renninger
2007-03-07 9:25 ` Alexander Clouter
2007-03-07 9:56 ` Len Brown
2007-03-07 21:09 ` Holger Macht
2007-03-07 15:43 ` Pallipadi, Venkatesh
2007-03-10 18:39 ` Thomas Renninger
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=20070307070208.GB15453@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=lenb@kernel.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 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.