linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-pm@vger.kernel.org, lkp@lists.01.org,
	Rafael Wysocki <rafael@kernel.org>
Subject: Re: [cpufreq] 909c0e9cc1: fwq.fwq.med 210.0% improvement
Date: Thu, 5 Mar 2020 08:50:00 +0100	[thread overview]
Message-ID: <951b0986-bb35-d9a5-1639-0a8cdb3dcd04@intel.com> (raw)
In-Reply-To: <20200305013509.GF5972@shao2-debian>

On 3/5/2020 2:35 AM, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a 210.0% improvement of fwq.fwq.med due to commit:

Well, that sounds impressive. :-)


>
> commit: 909c0e9cc11ba39fa5a660583b25c2431cf54deb ("cpufreq: intel_pstate: Use passive mode by default without HWP")
> https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git intel_pstate-passive
>
> in testcase: fwq
> on test machine: 16 threads Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz with 48G memory
> with following parameters:
>
> 	nr_task: 100%
> 	samples: 100000ss
> 	iterations: 18x
> 	cpufreq_governor: powersave

The governor should be schedutil, though, unless it is explicitly set to 
powersave in the test environment.

Is that the case?



  reply	other threads:[~2020-03-05  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  1:35 [cpufreq] 909c0e9cc1: fwq.fwq.med 210.0% improvement kernel test robot
2020-03-05  7:50 ` Rafael J. Wysocki [this message]
2020-03-05  8:18   ` Rong Chen
2020-03-05  9:05     ` Rafael J. Wysocki
2020-03-06  3:29       ` [LKP] " Huang, Ying
2020-03-06  9:54         ` Rafael J. Wysocki
2020-03-09  1:17           ` Huang, Ying
2020-03-10  8:45             ` Rafael J. Wysocki
2020-03-10  9:09               ` Huang, Ying

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=951b0986-bb35-d9a5-1639-0a8cdb3dcd04@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=devel@acpica.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=rafael@kernel.org \
    --cc=rong.a.chen@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;
as well as URLs for NNTP newsgroup(s).