[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25334395-d22e-4ff9-b393-7f776eb15d6a@intel.com>
Date: Thu, 13 Nov 2025 14:51:58 -0800
From: Reinette Chatre <reinette.chatre@...el.com>
To: Tony Luck <tony.luck@...el.com>, Fenghua Yu <fenghuay@...dia.com>, "Maciej
Wieczor-Retman" <maciej.wieczor-retman@...el.com>, Peter Newman
<peternewman@...gle.com>, James Morse <james.morse@....com>, Babu Moger
<babu.moger@....com>, Drew Fustini <dfustini@...libre.com>, Dave Martin
<Dave.Martin@....com>, Chen Yu <yu.c.chen@...el.com>
CC: <x86@...nel.org>, <linux-kernel@...r.kernel.org>,
<patches@...ts.linux.dev>
Subject: Re: [PATCH v13 26/32] fs/resctrl: Move allocation/free of
closid_num_dirty_rmid[]
Hi Tony,
On 10/29/25 9:21 AM, Tony Luck wrote:
> closid_num_dirty_rmid[] and rmid_ptrs[] are allocated together during resctrl
> initialization and freed together during resctrl exit.
>
> Telemetry events are enumerated on resctrl mount so only at resctrl mount will
> the number of RMID supported by all monitoring resources and needed as size for
> rmid_ptrs[] be known.
>
> Separate closid_num_dirty_rmid[] and rmid_ptrs[] allocation and free in
> preparation for rmid_ptrs[] to be allocated on resctrl mount.
>
> Keep the rdtgroup_mutex protection around the allocation and free of
> closid_num_dirty_rmid[] as ARM needs this to guarantee memory ordering.
>
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> ---
Reviewed-by: Reinette Chatre <reinette.chatre@...el.com>
Reinette
Powered by blists - more mailing lists