From: Yang Shi <yang@os.amperecomputing.com>
To: rafael@kernel.org, viresh.kumar@linaro.org,
george.cherian@cavium.com, pprakash@codeaurora.org
Cc: scott@os.amperecomputing.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [QUESTION] The delay between sampling for CPPC
Date: Mon, 20 Mar 2023 10:21:51 -0700 [thread overview]
Message-ID: <0453c753-681e-4d42-65e5-a5967697f6ca@os.amperecomputing.com> (raw)
Hi folks,
When testing CPPC cpufreq on our platform, we noticed the error may be
quite high and it (high error) may happen quite often. For example, our
platform max freq is 2.8GHz, when the CPUs were fully loaded (100%
load), we saw cpuinfo_cur_freq may show 4GHz, it means > 40% error. And
the high error (> 1%) happened 256 times out of 2127 samples (sampled
every 3 seconds) in 2hrs test.
We tried to change the delay to 100us, things got improved although we
still saw high error, but it happened much less often (22 times out of
3623 samples).
So why was 2us used as the delay? Does it make sense to use a larger
delay, for example, 100us used by our test, or even larger, for example,
ms granularity?
Thanks,
Yang
next reply other threads:[~2023-03-20 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 17:21 Yang Shi [this message]
2023-03-24 15:55 ` Yang Shi
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=0453c753-681e-4d42-65e5-a5967697f6ca@os.amperecomputing.com \
--to=yang@os.amperecomputing.com \
--cc=george.cherian@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--cc=rafael@kernel.org \
--cc=scott@os.amperecomputing.com \
--cc=viresh.kumar@linaro.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
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
all inboxes | Powered by JetHome®