From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>,
"'open list:DOCUMENTATION'" <linux-doc@vger.kernel.org>,
'Peter Zijlstra' <peterz@infradead.org>,
'Daniel Lezcano' <daniel.lezcano@linaro.org>,
'Giovanni Gherdovich' <ggherdovich@suse.cz>,
'Linux PM' <linux-pm@vger.kernel.org>,
Doug Smythies <dsmythies@telus.net>
Subject: RE: [PATCH] cpuidle: Add 'high' and 'low' idle state metrics
Date: Sat, 8 Dec 2018 08:36:07 -0800 [thread overview]
Message-ID: <000e01d48f14$21ca7020$655f5060$@net> (raw)
In-Reply-To: UpeTgvCH1QLjuUpeUg0j37
On 2018.12.06 01:09 Rafael J. Wysocki wrote:
> On Thu, Dec 6, 2018 at 12:08 AM Doug Smythies <dsmythies@telus.net> wrote:
>> On 2018.12.03 04:32 Rafael J. Wysocki wrote:
>>
>>> Add two new metrics for CPU idle states, "high" and "low", to count
>>> the number of times the given state had been asked for (or entered
>>> from the kernel's perspective), but the observed idle duration turned
>>> out to be too high or too low for it (respectively).
>>
>> I wonder about the "high" "low" terminology here.
>
> I took these names, because they are concise and simple. I could use
> "below" and "above" respectively I guess. What about these?
I see you already sent a new patch with these names. Yes, myself I like
them better.
I am going to try to add these counts to my next sets of graphs.
... Doug
next prev parent reply other threads:[~2018-12-08 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 23:07 [PATCH] cpuidle: Add 'high' and 'low' idle state metrics Doug Smythies
2018-12-06 9:08 ` Rafael J. Wysocki
2018-12-08 16:36 ` Doug Smythies [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-03 12:31 Rafael J. Wysocki
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='000e01d48f14$21ca7020$655f5060$@net' \
--to=dsmythies@telus.net \
--cc=daniel.lezcano@linaro.org \
--cc=ggherdovich@suse.cz \
--cc=linux-doc@vger.kernel.org \
--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 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).