From: Xiaochen Shen <shenxiaochen@open-hieco.net>
To: "Luck, Tony" <tony.luck@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"fenghuay@nvidia.com" <fenghuay@nvidia.com>
Cc: "babu.moger@amd.com" <babu.moger@amd.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"Dave.Martin@arm.com" <Dave.Martin@arm.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
shenxiaochen@open-hieco.net
Subject: Re: [PATCH 2/2] x86/resctrl: Fix memory bandwidth counter width for Hygon
Date: Sun, 7 Dec 2025 10:26:57 +0800 [thread overview]
Message-ID: <6a77f0dd-ea2a-4e2c-bf16-a3d660399051@open-hieco.net> (raw)
In-Reply-To: <e185be25-797a-4e98-b2b9-4acc963c321f@open-hieco.net>
Hi Tony,
On 12/7/2025 12:14 AM, Xiaochen Shen wrote:
>> Question: What is the value of "hw_res->mon_scale" on a Hygon system?
> I have double confirmed with Hygon hardware architect, in the testing Hygon system:
> hw_res->mon_scale: 64
> hw_res->mbm_width: 32
>
> Here is a rough calculation for the theoretical max bandwidth by the hardware counter:
> (1) 32-bits width and mon_scale is 64:
> 2 ^32 * 64 = 2 ^38 = 256 (B/s)
>
Sorry. Here is a typo:
- 2 ^32 * 64 = 2 ^38 = 256 (B/s)
+ 2 ^32 * 64 = 2 ^38 = 256G (B/s)
> (2) 24-bits width and mon_scale is 64 (this is highly likely to cause overflow):
> 2 ^24 * 64 = 2 ^30 = 1G (B/s)
Best regards,
Xiaochen Shen
next prev parent reply other threads:[~2025-12-07 2:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 2:37 [PATCH 0/2] x86/resctrl: Fix Platform QoS issues " Xiaochen Shen
2025-12-04 2:37 ` [PATCH 1/2] x86/resctrl: Add missing resctrl initialization " Xiaochen Shen
2025-12-06 3:30 ` Fenghua Yu
2025-12-06 10:47 ` Xiaochen Shen
2025-12-04 2:37 ` [PATCH 2/2] x86/resctrl: Fix memory bandwidth counter width " Xiaochen Shen
2025-12-04 17:11 ` Luck, Tony
2025-12-05 2:38 ` Xiaochen Shen
2025-12-05 20:33 ` Luck, Tony
2025-12-06 16:14 ` Xiaochen Shen
2025-12-07 2:26 ` Xiaochen Shen [this message]
2025-12-08 16:52 ` Luck, Tony
2025-12-07 0:56 ` Xiaochen Shen
2025-12-05 21:57 ` Reinette Chatre
2025-12-06 16:19 ` Xiaochen Shen
2025-12-04 23:30 ` [PATCH 0/2] x86/resctrl: Fix Platform QoS issues " Reinette Chatre
2025-12-05 2:47 ` Xiaochen Shen
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=6a77f0dd-ea2a-4e2c-bf16-a3d660399051@open-hieco.net \
--to=shenxiaochen@open-hieco.net \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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®