mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ping Li <leeonion.muyu@gmail.com>
To: james.morse@arm.com, ben.horgan@arm.com
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, reinette.chatre@intel.com,
	fenghuay@nvidia.com
Subject: arm_mpam: selecting hard or soft MBW_MAX limits
Date: Fri,  6 Nov 2026 12:36:11 +0800	[thread overview]
Message-ID: <20261106043611.790930-1-leeonion.muyu@gmail.com> (raw)

Hi Ben,

mbw_max support in the driver always programs MPAMCFG_MBW_MAX without
setting MPAMCFG_MBW_MAX.HARDLIM, so the limit is always soft: a
PARTID above its MAX contends with low priority for bandwidth beyond
the limit, but is not prevented from exceeding it. On our platform we
would like to be able to select the hard limit, where a PARTID above
its MAX is throttled even when the system is otherwise idle - soft
limits let a noisy task exceed its limit and disturb higher-priority
work when bandwidth contention appears.

MPAMF_MBW_IDR.MAXLIM reports whether the MSC implements a hard limit,
a soft limit, or both, but the driver does not read it today.

Is there a preferred way to expose this choice? The options we see:

  - a mount option or info flag, if the choice must be global
  - a per-resource or per-group resctrl knob
  - selecting hard limits by default whenever MAXLIM reports the MSC
    supports them

Thanks,
Ping

             reply	other threads:[~2026-11-06  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  4:36 Ping Li [this message]
2026-11-06  9:49 ` Ben Horgan

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=20261106043611.790930-1-leeonion.muyu@gmail.com \
    --to=leeonion.muyu@gmail.com \
    --cc=ben.horgan@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@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®