[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083F264B1730DBB86F06E1DFCAC9@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Tue, 28 Feb 2023 17:28:19 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: James Morse <james.morse@....com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
Peter Newman <peternewman@...gle.com>,
Jonathan Corbet <corbet@....net>,
"x86@...nel.org" <x86@...nel.org>
CC: Shaopeng Tan <tan.shaopeng@...itsu.com>,
Jamie Iles <quic_jiles@...cinc.com>,
Babu Moger <babu.moger@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: RE: [PATCH 4/7] x86/resctrl: Add code to setup monitoring at L3 or
NODE scope.
>> + /* When SNC enabled, monitor functions at node instead of L3 cache scope */
>> + if (snc_ways > 1)
>> + r = &rdt_resources_all[RDT_RESOURCE_NODE].r_resctrl;
>> + else
>> + r = &rdt_resources_all[RDT_RESOURCE_L3].r_resctrl;
>
> Could this be hidden in a helper with some name like resctrl_arch_get_mbm_resource()?
> You have the same pattern again in rdt_get_tree(). If this gets more complex in the
> future, it means its outside the filesystem code, and all in one place.
Sounds like a good idea. Thanks.
-Tony
Powered by blists - more mailing lists