From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Peter Newman <peternewman@google.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <dfustini@baylibre.com>,
Dave Martin <Dave.Martin@arm.com>,
Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Region aware RDT options for resctrl
Date: Mon, 14 Apr 2025 10:30:18 -0700 [thread overview]
Message-ID: <4bec8924-6125-45ef-a212-f123ab2e4f5b@intel.com> (raw)
In-Reply-To: <Z_mB-gmQe_LR4FWP@agluck-desk3>
Hi Tony,
Could you please help clarify how memory regions should be viewed?
On 4/11/25 1:56 PM, Luck, Tony wrote:
> On Fri, Apr 11, 2025 at 01:54:12PM -0700, Luck, Tony wrote:
>
> Add Cc: lkml
>
>> A future CPU from Intel will implement "region aware" memory bandwidth
>> monitoring and bandwidth allocation. This will provide for more granular
>> monitoring and control for heterogeneous memory configurations. BIOS
>> will populate an ACPI table that describes which system physical address
>> ranges belong to each region. E.g. for a two socket system with both
>> DDR and CXL memory regions could be assigned like this:
>>
>> Region 0: Local DDR
>> Region 1: Remote DDR
>> Region 2: Local CXL
>> Region 3: Remote CXL
If considering an assignment like above ...
...
>> Option 1: Per-memory regions might be described individually like this:
>>
>> $ cat schemata
>> RMB0:0=100;1=100
>> RMB1:0=75;1=75
>> RMB2:0=25;1=25
>>
... I assume "RMB0" represents "Region 0" and so forth. In this case, what do
the "domain IDs" used in above option represent?
Thank you.
Reinette
next prev parent reply other threads:[~2025-04-14 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z_mBcnAcGzMMvfxV@agluck-desk3>
2025-04-11 20:56 ` Region aware RDT options for resctrl Luck, Tony
2025-04-14 17:30 ` Reinette Chatre [this message]
2025-04-14 17:56 ` Luck, Tony
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=4bec8924-6125-45ef-a212-f123ab2e4f5b@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=babu.moger@amd.com \
--cc=dfustini@baylibre.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=peternewman@google.com \
--cc=tony.luck@intel.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