From: Zhang Rui <rui.zhang@intel.com>
To: Doug Smythies <dsmythies@telus.net>,
'Kajetan Puchalski' <kajetan.puchalski@arm.com>,
rafael@kernel.org
Cc: daniel.lezcano@linaro.org, lukasz.luba@arm.com,
Dietmar.Eggemann@arm.com, yu.chen.surf@gmail.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v4 0/2] cpuidle: teo: Introduce util-awareness
Date: Sun, 27 Nov 2022 00:43:24 +0800 [thread overview]
Message-ID: <f2b2b8da209a9cf22e80b089a698f78dd5c2f5fb.camel@intel.com> (raw)
In-Reply-To: <044424e924967a1c93649812b6e1670c8c37fce4.camel@intel.com>
> > Workflow: sleeping ebizzy 128 threads.
> > Variable: interval (uSecs).
> > Performance Results:
> > http://smythies.com/~doug/linux/idle/teo-util/graphs/ebizzy-128-perf.png
> > Performance power and idle data:
> > http://smythies.com/~doug/linux/idle/teo-util/ebizzy/perf/
>
> for the "Idle state 0/1/2/3 was too deep" graphs, may I know how you
> assert that an idle state is too deep/shallow?
>
is this got from the cpu_idle_miss trace event?
thanks,
rui
next prev parent reply other threads:[~2022-11-26 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 15:28 [RFC PATCH v4 0/2] cpuidle: teo: Introduce util-awareness Kajetan Puchalski
2022-11-02 15:28 ` [RFC PATCH v4 1/2] cpuidle: teo: Optionally skip polling states in teo_find_shallower_state() Kajetan Puchalski
2022-11-02 15:28 ` [RFC PATCH v4 2/2] cpuidle: teo: Introduce util-awareness Kajetan Puchalski
2022-11-21 12:22 ` [RFC PATCH v4 0/2] " Kajetan Puchalski
2022-11-21 12:50 ` Rafael J. Wysocki
2022-11-24 4:08 ` Doug Smythies
2022-11-26 16:26 ` Zhang Rui
2022-11-26 16:43 ` Zhang Rui [this message]
2022-11-26 21:56 ` Doug Smythies
2022-11-27 6:36 ` Zhang Rui
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=f2b2b8da209a9cf22e80b089a698f78dd5c2f5fb.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dsmythies@telus.net \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=yu.chen.surf@gmail.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).