From: Ben Horgan <ben.horgan@arm.com>
To: ben.horgan@arm.com
Cc: tony.luck@intel.com, reinette.chatre@intel.com, x86@kernel.org,
Dave.Martin@arm.com, james.morse@arm.com, babu.moger@amd.com,
fenghuay@nvidia.com, bp@alien8.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs/resctrl: Allocate rmid_ptrs[] using kvzalloc_objs()
Date: Wed, 16 Sep 2026 10:26:05 +0100 [thread overview]
Message-ID: <cfc17679-c8a9-4ac4-bb90-6b336bd91407@arm.com> (raw)
In-Reply-To: <20260911160608.1091121-1-ben.horgan@arm.com>
I realised I forgot to include a changelog with this v2. The only change from v1 is an update to the
fixes tag as suggested by Reinette.
Thanks,
Ben
On 11/09/2026 17:06, Ben Horgan wrote:
> On an MPAM system the number of entries in rmid_ptrs[] is the number of PARTIDs
> multiplied by the number of PMGs. The maximum possible number of PARTIDs is
> 0x10000 and the maximum number of PMGs is 0x100. On a system pushing the limits
> of the MPAM specification this can be large enough to consistently fail the
> kzalloc_objs() allocation and hence fail to mount the resctrl filesystem.
>
> Switch to allocating rmid_ptrs[] using kvzalloc_objs() so that large allocations
> fall back to vmalloc().
>
> Fixes: 264c285999fc ("arm_mpam: resctrl: Add monitor initialisation and domain boilerplate")
> Signed-off-by: Ben Horgan <ben.horgan@arm.com>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
> ---
> I found this by testing the extremes of a software model and don't expect this
> to effect real systems.
> ---
> fs/resctrl/monitor.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/resctrl/monitor.c b/fs/resctrl/monitor.c
> index 73413cb128ea..2d7df60973d1 100644
> --- a/fs/resctrl/monitor.c
> +++ b/fs/resctrl/monitor.c
> @@ -979,7 +979,7 @@ int setup_rmid_lru_list(void)
> return 0;
>
> idx_limit = resctrl_arch_system_num_rmid_idx();
> - rmid_ptrs = kzalloc_objs(struct rmid_entry, idx_limit);
> + rmid_ptrs = kvzalloc_objs(struct rmid_entry, idx_limit);
> if (!rmid_ptrs)
> return -ENOMEM;
>
> @@ -1010,7 +1010,7 @@ void free_rmid_lru_list(void)
> return;
>
> mutex_lock(&rdtgroup_mutex);
> - kfree(rmid_ptrs);
> + kvfree(rmid_ptrs);
> rmid_ptrs = NULL;
> mutex_unlock(&rdtgroup_mutex);
> }
next prev parent reply other threads:[~2026-09-16 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 16:06 Ben Horgan
2026-09-16 9:26 ` Ben Horgan [this message]
2026-09-16 16:52 ` Reinette Chatre
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=cfc17679-c8a9-4ac4-bb90-6b336bd91407@arm.com \
--to=ben.horgan@arm.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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®