From: Reinette Chatre <reinette.chatre@intel.com>
To: Amit Singh Tomar <amitsinght@marvell.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <fenghua.yu@intel.com>, <james.morse@arm.com>,
<gcherian@marvell.com>, <robh@kernel.org>,
<peternewman@google.com>, "Luck, Tony" <tony.luck@intel.com>
Subject: Re: [RFC 00/12] ARM: MPAM: add support for priority partitioning control
Date: Thu, 17 Aug 2023 13:29:37 -0700 [thread overview]
Message-ID: <ddbc280a-1a53-b6ce-ea83-5b08eb1f5c6f@intel.com> (raw)
In-Reply-To: <f0e10f31-8571-baf6-6665-b077af067777@intel.com>
Hi Amit,
On 8/17/2023 12:11 PM, Reinette Chatre wrote:
> On 8/15/2023 8:27 AM, Amit Singh Tomar wrote:
>>
>> Within the DDR QoS traffic class.
>>
>> 0--5 ----> Low priority value
>> 6-10 ----> Medium priority value
>> 11-15 ----> High priority value
>>
>> Benchmark[4] used is multichase.
>>
>> Two partition P1 and P2:
>>
>> Partition P1:
>> -------------
>> Assigned core 0
>> 100% BW assignment
>>
>> Partition P2:
>> -------------
>> Assigned cores 1-79
>> 100% BW assignment
>>
>> Test Script:
>> -----------
>> mkdir p1
>> cd p1
>> echo 1 > cpus
>> echo L3:1=8000,5 > schemata ##### DSPRI set as 5 (lpr)
>> echo "MB:0=100" > schemata
I peeked at the next commit and I am missing something.
It looks like indeed resource instances need to
support different controls, so that seems to answer my earlier
question. How to let user know what is supported where
remains an open, now with understanding that the information
is required to be per resource instance.
The first commit mentions that #0 has the Priority
partitioning feature but in these examples the schemata
of #1 is updated to modify the priority. Also, if I
understand correctly CPOR and priority partitioning
are mutually exclusive so I find it confusing to
see a bitmap and a priority written to a single resource.
Reinette
next prev parent reply other threads:[~2023-08-17 20:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 15:27 Amit Singh Tomar
2023-08-15 15:27 ` [RFC 01/12] arm_mpam: Handle resource instances mapped to different controls Amit Singh Tomar
2023-09-01 12:39 ` Jonathan Cameron
2023-08-15 15:27 ` [RFC 02/12] arm_mpam: resctrl: Detect priority partitioning capability Amit Singh Tomar
2023-09-01 12:30 ` Jonathan Cameron
2023-08-15 15:27 ` [RFC 03/12] arm_mpam: resctrl: Define new schemata format for priority partition Amit Singh Tomar
2023-08-15 15:27 ` [RFC 04/12] fs/resctrl: Obtain CPBM upon priority partition presence Amit Singh Tomar
2023-08-15 15:27 ` [RFC 05/12] fs/resctrl: Set-up downstream priority partition resources Amit Singh Tomar
2023-08-17 17:39 ` Fenghua Yu
2023-08-15 15:27 ` [RFC 06/12] fs/resctrl: Extend schemata read for priority partition control Amit Singh Tomar
2023-08-17 17:42 ` Fenghua Yu
2023-08-15 15:27 ` [RFC 07/12] arm_mpam: resctrl: Retrieve priority values from arch code Amit Singh Tomar
2023-08-15 15:27 ` [RFC 08/12] fs/resctrl: Schemata write only for intended resource Amit Singh Tomar
2023-08-15 15:27 ` [RFC 09/12] fs/resctrl: Extend schemata write for priority partition control Amit Singh Tomar
2023-08-17 17:27 ` Fenghua Yu
2023-08-17 17:53 ` Fenghua Yu
2023-08-15 15:27 ` [RFC 10/12] arm_mpam: resctrl: Facilitate writing downstream priority value Amit Singh Tomar
2023-08-15 15:27 ` [RFC 11/12] arm_mpam: Fix Downstream priority mask Amit Singh Tomar
2023-09-01 13:32 ` Jonathan Cameron
2023-08-15 15:27 ` [RFC 12/12] arm_mpam: Program Downstream priority value Amit Singh Tomar
2023-09-01 13:17 ` Jonathan Cameron
2023-08-17 19:11 ` [RFC 00/12] ARM: MPAM: add support for priority partitioning control Reinette Chatre
2023-08-17 20:29 ` Reinette Chatre [this message]
2023-08-22 12:44 ` [EXT] " Amit Singh Tomar
2023-08-23 19:06 ` Reinette Chatre
2023-08-23 21:33 ` Amit Singh Tomar
2023-08-23 22:20 ` Reinette Chatre
2023-08-23 22:36 ` Luck, Tony
2023-08-24 8:52 ` Amit Singh Tomar
2023-08-24 15:30 ` Luck, Tony
2023-08-24 18:00 ` Reinette Chatre
2024-01-11 20:56 ` Peter Newman
2024-01-11 21:40 ` Tony Luck
2024-01-11 22:01 ` Reinette Chatre
2024-01-11 23:14 ` Luck, Tony
2024-01-11 23:31 ` Reinette Chatre
2023-08-22 9:01 ` Peter Newman
2023-09-01 14:42 ` Jonathan Cameron
2023-09-01 15:04 ` Jonathan Cameron
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=ddbc280a-1a53-b6ce-ea83-5b08eb1f5c6f@intel.com \
--to=reinette.chatre@intel.com \
--cc=amitsinght@marvell.com \
--cc=fenghua.yu@intel.com \
--cc=gcherian@marvell.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®