All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH v3 29/31] tunables: removed on-demand cpu frequency governor
Date: Fri, 13 Dec 2013 10:43:49 -0800	[thread overview]
Message-ID: <20131213104349.47f57798@kcaccard-desk.amr.corp.intel.com> (raw)
In-Reply-To: 20131210202752.GE2422@swordfish

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

On Tue, 10 Dec 2013 23:27:52 +0300
Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com> wrote:

> On (11/18/13 12:27), Alexandra Yates wrote:
> > Remove suggestion to use the on-demand cpu frequency governor from
> > PowerTOP tunables as that is no longer a good suggestion since the
> > P-State driver is the Intel recommended replacement.
> 
> I need to think about it.
> 
> IIRC, in this email
> https://lists.01.org/pipermail/powertop/2013-September/000952.html
> 
> Christian Krause wrote:
> 
> >
> >tunables show:
> >
> >    Bad           Using 'ondemand' cpufreq governor
> >
> >but: I don't have a ondemand cpufreq governor -- that is what I just found out: since some kernel
> >versions ago the intel_pstate driver is the default for my cpu:
> >
> >    # zgrep PSTATE /proc/config.gz
> >    CONFIG_X86_INTEL_PSTATE=y
> >
> >    # cat /sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_driver
> >    intel_pstate
> >    intel_pstate
> >    intel_pstate
> >    intel_pstate
> >
> 
> 
> 
> I'm not really sure why we delete cpufreq code and kill this feature.
> 
> 
> 
> for example:
> 
> $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
> ondemand performance
> 
> $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> performance
> 
> 
> 
> powertop can help here
> 
> 
> 	-ss
> 

Actually, in most cases using performance would be preferred over
ondemand unless you are on ancient hardware.  You may be interested in
reading this article which sort of summarizes the situation.

http://www.phoronix.com/scan.php?page=news_item&px=MTM3NDQ



             reply	other threads:[~2013-12-13 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 18:43 Kristen Carlson Accardi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-10 20:27 [Powertop] [PATCH v3 29/31] tunables: removed on-demand cpu frequency governor Sergey Senozhatsky
2013-11-18 20:27 Alexandra Yates

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=20131213104349.47f57798@kcaccard-desk.amr.corp.intel.com \
    --to=powertop@lists.01.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.