[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OSBPR01MB203754574F2AC6281EFA1FDE80209@OSBPR01MB2037.jpnprd01.prod.outlook.com>
Date: Wed, 26 Jan 2022 09:24:35 +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: [PATCH 0/8] Add hardware prefetch control driver for arm64 and
x86
> Doesn't this break the one-value-per-file sysfs rules?
Sorry, I forgot the sysfs rules.
The current interface specification was decided referring to the
specification of /sys/class/rnbd-client/ctl/map_device. However,
I thought that the current specification of preftch_control was
inappropriate because it relevant to "Mixing types, expressing
multiple lines of data" in Documentation/filesystems/sysfs.rst.
The next version patch divides the attribute file by option, as
described below.
* Current version interface
```
/sys/devices/system/cpu/cpu0/cache/index0/
prefetch_control (attribute file)
```
* Next version interface look like this
```
/sys/devices/system/cpu/cpu0/cache/index0/prefetch_control/
hardware_prefetcher_enable (attribute file)
ip_prefetcher_enable (attribute file)
```
Powered by blists - more mailing lists