mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shaopeng Tan (Fujitsu)" <tan.shaopeng@fujitsu.com>
To: "James Morse <james.morse@arm.com>" <james.morse@arm.com>,
	Zeng Heng <zengheng4@huawei.com>,
	"ben.horgan@arm.com" <ben.horgan@arm.com>,
	"Dave.Martin@arm.com" <Dave.Martin@arm.com>,
	"reinette.chatre@intel.com" <reinette.chatre@intel.com>,
	"fenghuay@nvidia.com" <fenghuay@nvidia.com>,
	"tglx@kernel.org" <tglx@kernel.org>,
	"will@kernel.org" <will@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>, "bp@alien8.de" <bp@alien8.de>,
	"babu.moger@amd.com" <babu.moger@amd.com>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"gshan@redhat.com" <gshan@redhat.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>
Subject: Re: Re: [PATCH v8 next 04/10] arm_mpam: Refactor rmid to reqPARTID/PMG mapping
Date: Thu, 8 Oct 2026 04:30:54 +0000	[thread overview]
Message-ID: <TY4PR01MB169308CED201FDC318438FAAE8B932@TY4PR01MB16930.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <2944b506-a462-42f8-95cf-404241fb27f0@arm.com>

Hello Zeng,

> The reason of using base_partid as MPARTID_lo is to keep base_partid
> contiguous and CLOSIDs are allocated contiguously. This does mean
> MPARTIDs under the same CPARTID won't be contiguous, but that's
> inherently difficult to guarantee with dynamic allocation anyway.
> 
> 
> The control path uses CLOSID alone (CPARTID), and the monitor path uses
> RMID alone (the (MPARTID, PMG) pair). This definition also aligns
> closely with the native resctrl concepts: CLOSID (Class of Service ID,
> corresponding to CPARTID) and RMID (Resource Monitor ID, corresponding
> to the (MPARTID, PMG) pair).
> 
> 
> In the end, the number of control groups is determined by the number of
> CPARTIDs. Both of these ID translation schemes support multiple control
> groups.
> 
> Could you please help outline the pros and cons of each approach?
> This will determine which direction I take for subsequent iterations.

I think the fundamental difference between these two approaches 
lies in whether the  allocation is static or dynamic. 
I proposed a similar idea to James and Dave about two years ago.
I agree that your proposal for dynamic allocation is excellent
in terms of flexibility and resource utilization.

However, dynamically assigning MPARTID_hi and MPARTID_lo upon 
the creation or deletion of a control/monitoring group would likely 
require extensive modifications to the resctrl core code.
In particular, with the integration of PARTID Narrowing occurring 
alongside major changes to the resctrl interface, 
there is a risk that these modifications might interfere with
each other and lead to complications.

To ensure a smooth and timely merge, would it be better to proceed
in stages - first implementing static allocation and then 
transitioning to dynamic allocation afterward? 
What do you think?

Best regards,
Shaopeng TAN 

  parent reply	other threads:[~2026-10-08  4:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  8:53 [PATCH v8 next 00/10] arm_mpam: Introduce Narrow-PARTID feature Zeng Heng
2026-04-13  8:53 ` [PATCH v8 next 01/10] fs/resctrl: Fix MPAM Partid parsing errors by preserving CDP state during umount Zeng Heng
2026-05-14 17:06   ` James Morse
2026-05-20 12:16     ` Zeng Heng
2026-05-20 12:28       ` Zeng Heng
2026-04-13  8:53 ` [PATCH v8 next 02/10] arm_mpam: Add intPARTID and reqPARTID support for Narrow-PARTID feature Zeng Heng
2026-05-14 17:06   ` James Morse
2026-05-22 10:07     ` Zeng Heng
2026-04-13  8:53 ` [PATCH v8 next 03/10] arm_mpam: Disable reqPARTID expansion when Narrow-PARTID is unavailable Zeng Heng
2026-05-14 17:06   ` James Morse
2026-05-22  9:57     ` Zeng Heng
2026-04-13  8:53 ` [PATCH v8 next 04/10] arm_mpam: Refactor rmid to reqPARTID/PMG mapping Zeng Heng
2026-05-14 17:07   ` James Morse
2026-06-12  8:44     ` Zeng Heng
2026-06-13  2:57       ` [PATCH v8 next 04/10 Resend] " Zeng Heng
2026-06-13  8:59       ` [PATCH v8 next 04/10 Resend v2] " Zeng Heng
2026-10-08  4:30     ` Shaopeng Tan (Fujitsu) [this message]
2026-04-13  8:54 ` [PATCH v8 next 05/10] arm_mpam: Propagate control group config to sub-monitoring groups Zeng Heng
2026-04-13  8:54 ` [PATCH v8 next 06/10] arm_mpam: Add boot parameter to limit mpam_intpartid_max Zeng Heng
2026-04-13  8:54 ` [PATCH v8 next 07/10] fs/resctrl: Add rmid_entry state helpers Zeng Heng
2026-04-13  8:54 ` [PATCH v8 next 08/10] arm_mpam: Implement dynamic reqPARTID allocation for monitoring groups Zeng Heng
2026-04-13  8:54 ` [PATCH v8 next 09/10] fs/resctrl: Wire up rmid expansion and reclaim functions Zeng Heng
2026-04-13  8:54 ` [PATCH v8 next 10/10] arm_mpam: Add mpam_sync_config() for dynamic rmid expansion Zeng Heng
2026-04-16  6:29 ` [PATCH v8 next 00/10] arm_mpam: Introduce Narrow-PARTID feature Shaopeng Tan (Fujitsu)
2026-04-20  7:31 ` Zeng Heng
2026-04-28  4:20   ` Shaopeng Tan (Fujitsu)
2026-04-29  9:47     ` Zeng Heng
2026-04-29 10:59 ` Zeng Heng
2026-05-14 17:06 ` James Morse
2026-05-20  9:47   ` Zeng Heng

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=TY4PR01MB169308CED201FDC318438FAAE8B932@TY4PR01MB16930.jpnprd01.prod.outlook.com \
    --to=tan.shaopeng@fujitsu.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=ben.horgan@arm.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghuay@nvidia.com \
    --cc=gshan@redhat.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=reinette.chatre@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=zengheng4@huawei.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®