[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OSBPR01MB20377DD32D4E285CCEC3629480939@OSBPR01MB2037.jpnprd01.prod.outlook.com>
Date: Wed, 10 Nov 2021 09:25:20 +0000
From: "tarumizu.kohei@...itsu.com" <tarumizu.kohei@...itsu.com>
To: 'Dave Hansen' <dave.hansen@...el.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH v2 5/5] docs: ABI: Add sysfs documentation interface
of hardware prefetch driver
> First, I'd give them real names.
>
> Second, I'd link them to the level or levels of the cache that they effect.
>
> Third, I'd make sure that it is clear what caches it affects.
>
> We have a representation of the caches in:
>
> /sys/devices/system/cpu/cpu*/cache
>
> It would be a shame to ignore those.
Thank you for your advice.
I try to reconsider the design.
Powered by blists - more mailing lists