mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Voegtle <thomas@voegtle-clan.de>
To: "Longepe, Philippe" <philippe.longepe@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Gasparini, Stephane" <stephane.gasparini@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: RE: Performance drop on Baytrail with 4.5-rc2
Date: Wed, 3 Feb 2016 20:18:21 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.11.1602032001430.8870@er-systems.de> (raw)
In-Reply-To: <8B729BF8A98FF048A53185F813A469D935B1A189@HASMSX105.ger.corp.intel.com>

On Wed, 3 Feb 2016, Longepe, Philippe wrote:

> Thank you for sharing this test. I just did a quick test and yes this is 
> really interesting !
>
> Without the scale option, the load is close to 100% for each cpus (so 
> the pstates are increasing up to the turbo frequency) but with 
> scale=320:208, the load is oscillating (close to 50% in average), so the 
> requested frequencies are lower (the power is also reduced).
>
> I have a patch (not yet submitted) that reduce the gap for such a use case.

That's nice, glad the benchmark helped.

> As a temporary solution, you can also switch to performance with:
>
> sudo su
> echo performance > /sys/devices/system/cpu/cpu*/scaling_governor

Yes, ok, thanks.

> However, I still don't know why there is 50% of idle with the scale 
> option (is it using a Hw accelerator ?).


Mh. I don't know. I always thought this is stuff which is not that 
threadable as the mpeg to mp4 conversion, or something like that?


Thanks,

   Thomas

  parent reply	other threads:[~2016-02-03 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 20:34 Thomas Voegtle
2016-02-02 10:33 ` Longepe, Philippe
2016-02-02 17:56   ` Thomas Voegtle
     [not found]     ` <8B729BF8A98FF048A53185F813A469D935B1A189@HASMSX105.ger.corp.intel.com>
2016-02-03 19:18       ` Thomas Voegtle [this message]
2016-03-13 15:54       ` Thomas Voegtle
2016-03-15  8:52         ` Longepe, Philippe

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=alpine.LSU.2.11.1602032001430.8870@er-systems.de \
    --to=thomas@voegtle-clan.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.longepe@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stephane.gasparini@intel.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

all inboxes | Powered by JetHome®