From: John Kacur <jkacur@redhat.com>
To: EnDe Tan <ende.tan@starfivetech.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"williams@redhat.com" <williams@redhat.com>,
Leyfoon Tan <leyfoon.tan@starfivetech.com>,
"endeneer@gmail.com" <endeneer@gmail.com>
Subject: RE: [1/1] rt-tests: determine_maximum_mpps.sh: Introduce '-F' option to specify CPU frequency
Date: Thu, 12 Dec 2024 10:48:14 -0500 (EST) [thread overview]
Message-ID: <39f55b99-a8c7-5941-ee82-442e2cd9ead7@redhat.com> (raw)
In-Reply-To: <NT0PR01MB1024694086DE4C6265BF22DEF83FA@NT0PR01MB1024.CHNPR01.prod.partner.outlook.cn>
On Thu, 12 Dec 2024, EnDe Tan wrote:
> > Are there other places to get this information, for example
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
> It is possible to specify "clock-frequency" in CPU nodes in device tree,
> which corresponds to entry like this
> /sys/devices/system/cpu/cpu0/of_node/clock-frequency
>
> However, it's not mandatory to specify "clock-frequency", so maybe
> adding a '-F' option is more useful.
>
>
But why we would want to allow the user to specify a potentially arbitrary
number, when we can get a more accurate one from the OS?
Do you have any comments Marcelo?
John
prev parent reply other threads:[~2024-12-12 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 17:11 [1/1] rt-tests: determine_maximum_mpps.sh: Introduce '-F' option to specify CPU frequency ende.tan
2024-12-11 19:25 ` John Kacur
2024-12-12 5:43 ` EnDe Tan
2024-12-12 15:48 ` John Kacur [this message]
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=39f55b99-a8c7-5941-ee82-442e2cd9ead7@redhat.com \
--to=jkacur@redhat.com \
--cc=ende.tan@starfivetech.com \
--cc=endeneer@gmail.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=williams@redhat.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).