Linux-PM Archive on lore.kernel.org
 help / color / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Doug Smythies <dsmythies@telus.net>
Cc: "'Rafael J. Wysocki'" <rafael@kernel.org>,
	'kernel list' <linux-kernel@vger.kernel.org>,
	'ACPI Devel Maling List' <linux-acpi@vger.kernel.org>,
	"'Zhang, Rui'" <rui.zhang@intel.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	'Viresh Kumar' <viresh.kumar@linaro.org>,
	'Linux PM' <linux-pm@vger.kernel.org>,
	'Thomas Gleixner' <tglx@linutronix.de>,
	'Ingo Molnar' <mingo@redhat.com>,
	'Borislav Petkov' <bp@alien8.de>,
	"'H. Peter Anvin'" <hpa@zytor.com>,
	'the arch/x86 maintainers' <x86@kernel.org>
Subject: Re: 5.2-rc2: low framerate in flightgear, cpu not running at full speed, thermal related?
Date: Thu, 13 Jun 2019 10:11:58 +0200
Message-ID: <20190613081158.GA6853@amd> (raw)
In-Reply-To: <008f01d52178$07b3be70$171b3b50$@net>

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

Hi!

> On 2019.06.12 14:25 Rafael J. Wysocki wrote:
> > On Wed, Jun 12, 2019 at 4:45 AM Doug Smythies <dsmythies@telus.net> wrote:
> >>
> >> So, currently there seems to be 3 issues in this thread
> >> (and I am guessing a little, without definitive data):
> >>
> >> 1.) On your system Kernel 5.4-rc2 (or 4) defaults to the intel_pstate CPU frequency
> >> scaling driver and the powersave governor, but kernel 4.6 defaults to the
> >> acpi-cpufreq CPU frequency scaling driver and the ondemand governor.
> >
> > Which means that intel_pstate works in the active mode by default and
> > so it uses its internal governor.
> 
> Note sure what you mean by "internal governor"?
> If you meant HWP (Hardware P-state), Pavel's processor doesn't have it.
> If you meant the active powersave governor code within the driver, then agreed.
> 
> > That governor is more performance-oriented than ondemand and it very
> > well may cause more power to be allocated for the processor - at the
> > expense of the GPU.
> 
> O.K. I mainly use servers and so have no experience with possible GPU
> verses CPU tradeoffs.
> 
> However, I did re-do my tests measuring energy instead of CPU frequency
> and found very little difference between the acpi-cpufreq/ondemand verses
> intel_pstate/powersave as a function of single threaded load. Actually,
> I did the test twice, one at 20 hertz work/sleep frequency and also
> at 67 hertz work/sleep frequency. (Of course, Pavel's processor might
> well have a different curve, but it is a similar vintage to mine
> i5-2520M verses i7-2600K.) The worst difference was approximately
> 1.1 extra processor package watts (an extra 5.5%) in the 80% to 85%
> single threaded load range at 67 hertz work/sleep frequency for
> the intel-pstate/powersave driver/governor. 
> 
> What am I saying? For a fixed amount of work to do per work/sleep cycle
> (i.e. maybe per video frame related type work) while the CPU frequency Verses load
> curves might differ, the resulting processor energy curve differs much less.
> (i.e. the extra power for higher CPU frequency is for less time because it gets
> the job done faster.) So, myself, I don't yet understand why only the one method
> would have hit thermal throttling, but not the other (if indeed it
> doesn't).

It seems there are serious differences in reporting :-(. How do I
determine which frequency CPU really runs at, in 4.6 kernel?

But it seems that your assumptions are incorrect for my workload.

flightgear is single-threaded, and in my configuration saturates the
CPU, because it would like to achieve higher framerate than my system
is capable of.

> Just for information: CPU frequency verses single threaded load curves
> for the conservative governor is quite different between the two drivers.
> (tests done in February, perhaps I should re-do and also look at energy
> at the same time, or instead of CPU frequency.)

So this might be my problem?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 11:17 Pavel Machek
2019-06-09 11:23 ` Pavel Machek
2019-06-09 12:12   ` Pavel Machek
2019-06-09 13:55     ` Daniel Lezcano
2019-06-09 14:13     ` Zhang Rui
2019-06-11 10:12       ` Pavel Machek
2019-06-11 10:15         ` Viresh Kumar
2019-06-12  2:37 ` Doug Smythies
2019-06-12 21:44   ` Rafael J. Wysocki
2019-06-12 23:39     ` Doug Smythies
2019-06-13  8:11       ` Pavel Machek [this message]
2019-06-13  9:00         ` Rafael J. Wysocki
2019-06-13  8:52       ` Rafael J. Wysocki
2019-06-18  8:20         ` Doug Smythies
2019-06-18  8:34           ` Pavel Machek

Reply instructions:

You may reply publically 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=20190613081158.GA6853@amd \
    --to=pavel@ucw.cz \
    --cc=bp@alien8.de \
    --cc=dsmythies@telus.net \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@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

Linux-PM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-pm/0 linux-pm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-pm linux-pm/ https://lore.kernel.org/linux-pm \
		linux-pm@vger.kernel.org linux-pm@archiver.kernel.org
	public-inbox-index linux-pm


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-pm


AGPL code for this site: git clone https://public-inbox.org/ public-inbox