[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DS7PR11MB6077FDF2B6EEC736D6506C7AFC1DA@DS7PR11MB6077.namprd11.prod.outlook.com>
Date: Thu, 24 Aug 2023 15:30:54 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Amit Singh Tomar <amitsinght@...vell.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
CC: "Yu, Fenghua" <fenghua.yu@...el.com>,
"james.morse@....com" <james.morse@....com>,
George Cherian <gcherian@...vell.com>,
"robh@...nel.org" <robh@...nel.org>,
"peternewman@...gle.com" <peternewman@...gle.com>
Subject: RE: [EXT] Re: [RFC 00/12] ARM: MPAM: add support for priority
partitioning control
> 2) Second approach that we discussed internally is to have schemata for CPOR, and PPART separated by new line as mentioned/suggested by Peter, But it may require to tweak
> the ARM MPAM device driver a bit. It was kind of toss-up between 2nd and 3nd approach :), and we went with the 3rd one.
>
> L3:0=XXXX
> L3:0=PPART=X
>
> Will look into it again.
That looks hard to parse. How about:
L3:0=XXX;1=YYY
L3PPART:0=AAA;1=BBB
L3CPOR:0=MMM;1=NNN
-Tony
Powered by blists - more mailing lists