mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yin Li <yin.li@oss.qualcomm.com>
To: Ping Li <leeonion.muyu@gmail.com>
Cc: sdonthineni@nvidia.com, james.morse@arm.com, robh@kernel.org,
	ben.horgan@arm.com, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 6/7] arm_mpam: Add support for memory controller MSC on DT platforms
Date: Wed, 11 Nov 2026 17:42:23 +0800	[thread overview]
Message-ID: <f8911f68-ee78-4eb2-b7e5-1e879224091d@oss.qualcomm.com> (raw)
In-Reply-To: <20261109112737.1081437-1-leeonion.muyu@gmail.com>



On 11/9/2026 7:27 PM, Ping Li wrote:
> Tested-by: Ping Li <leeonion.muyu@gmail.com>


Hi Ping,

Thank you for the Tested-by — it really helps move v5 forward.

To help the maintainers evaluate this series more quickly, could you
share some additional information about your use case?

1. Your SoC or platform name (if publicly available), or a brief
    description (e.g. "server SoC with an MPAM MSC on the DDR egress
    path").
2. The typical workload scenario where memory bandwidth QoS is useful
    for you (e.g. isolating bandwidth between tenants, preventing certain
    workloads from saturating DDR, etc.).
3. Which specific features did you verify on v5? (MSC probe, resctrl
    mount, MB allocation, mbm_total_bytes monitoring, etc.)

A real usage log showing the memory controller MSC working through
resctrl would also be very helpful — similar to what we have for the
cache MSC:

```
root@qcom-armv8a:/sys/fs/resctrl# cat schemata
     L2:0=fff;65536=fff;131072=fff
root@qcom-armv8a:/sys/fs/resctrl# echo "L2:0=111;65536=222;131072=333" > 
schemata
root@qcom-armv8a:/sys/fs/resctrl# cat schemata
     L2:0=111;65536=222;131072=333
root@qcom-armv8a:/sys/fs/resctrl#
```

This would give the maintainers a clearer picture of the real-world
value of these patches and help speed up the review.

Thanks,
Yin

-- 
Thx and BRs,
Yin


  reply	other threads:[~2026-11-11  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 10:05 [PATCH v5 0/7] arm-mpam: Add basic device tree support for resctrl Yin Li
2026-11-09 10:05 ` [PATCH v5 1/7] arm_mpam: Fix the RIS index range check in mpam_ris_create_locked Yin Li
2026-11-09 10:05 ` [PATCH v5 2/7] arm_mpam: Fix MSC MMIO window size off-by-one with resource_size() Yin Li
2026-11-09 10:05 ` [PATCH v5 3/7] dt-bindings: arm: Add MPAM MSC binding Yin Li
2026-11-09 10:05 ` [PATCH v5 4/7] cacheinfo: Expose the code to generate a cache-id from a device_node Yin Li
2026-11-09 10:05 ` [PATCH v5 5/7] arm_mpam: Add device tree support for MSC probing Yin Li
2026-11-09 10:05 ` [PATCH v5 6/7] arm_mpam: Add support for memory controller MSC on DT platforms Yin Li
2026-11-09 11:27   ` Ping Li
2026-11-11  9:42     ` Yin Li [this message]
2026-11-09 10:05 ` [PATCH v5 7/7] arm64: dts: qcom: nord: Add MPAM MSC nodes for the L2 caches Yin Li

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=f8911f68-ee78-4eb2-b7e5-1e879224091d@oss.qualcomm.com \
    --to=yin.li@oss.qualcomm.com \
    --cc=ben.horgan@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=james.morse@arm.com \
    --cc=leeonion.muyu@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sdonthineni@nvidia.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®