All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Peter Zijlstra'" <peterz@infradead.org>,
	"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	"'Giovanni Gherdovich'" <ggherdovich@suse.cz>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	"'Linux PM'" <linux-pm@vger.kernel.org>
Subject: RE: [PATCH v2] cpuidle: Use nanoseconds as the unit of time
Date: Fri, 8 Nov 2019 09:04:33 -0800	[thread overview]
Message-ID: <000a01d59656$99798710$cc6c9530$@net> (raw)
In-Reply-To: <CAJZ5v0gsK0OmqAvw2BVGvajPmCTrRGFVVZ0+Y99ZkbbUcWYGOg@mail.gmail.com>

On 2019.11.08 01:45 Rafael J. Wysocki wrote:
> On Fri, Nov 8, 2019 at 9:45 AM Doug Smythies <dsmythies@telus.net> wrote:
>
...
>> I have been running this v2 today, with both menu and teo
>> governors. Acquiring some baseline reference data to compare
>> to now. The menu governor response seems different (Supporting
>> information/graphs will come later).
>
> That may be good or bad, depending in what way it is different. :-)

My thinking was that the differences should be minimal between
the baseline (linux-next as of 2019.11.07) and plus your two patches.
Because this was a change of units, but not functionality.
Such is the case with the teo governor, but not the menu governor.
I have not tried the ladder or haltpoll governors, and don't intend to.

Now to attempt to isolate the issue in the code, which might take
considerable time.

The test in question was that sweep one developed during the
powernightmare stuff. It is a crude attempt to sweep through
a preference for all idle states. While not a great test, who cares
if it reveals something.

Reference:
http://www.smythies.com/~doug/linux/idle/nano-second-conversion/sweep/index.html

Legend:
teo-base : linux-next 2019.11.07
menu-base: linux-next 2019.11.07
teo-v2   : linux-next 2019.11.07 + cpuidle: Consolidate disabled state checks + this v2
menu-v2  : linux-next 2019.11.07 + cpuidle: Consolidate disabled state checks + this v2

Note: I only tossed the graphs there, without a way to navigate to the location
from the parent web pages.

... Doug



  reply	other threads:[~2019-11-08 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 10:30 [PATCH] cpuidle: Use nanoseconds as the unit of time Rafael J. Wysocki
2019-11-07 14:25 ` [PATCH v2] " Rafael J. Wysocki
2019-11-08  1:44   ` Rafael J. Wysocki
2019-11-08  8:45     ` Doug Smythies
2019-11-08  9:45       ` Rafael J. Wysocki
2019-11-08 17:04         ` Doug Smythies [this message]
2019-11-10 16:48           ` Rafael J. Wysocki
2019-11-10 17:24             ` Rafael J. Wysocki
2019-11-10 18:09               ` Doug Smythies
2019-11-10 22:12                 ` Doug Smythies
2019-11-11 21:29                   ` Rafael J. Wysocki
2019-11-08  9:39     ` Peter Zijlstra

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='000a01d59656$99798710$cc6c9530$@net' \
    --to=dsmythies@telus.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=ggherdovich@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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.