[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cfb43e6138a62889fd5ba9683c93e10ee32635df.camel@wdc.com>
Date: Mon, 4 Jun 2018 08:31:16 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"evgreen@...omium.org" <evgreen@...omium.org>,
"vinholikatti@...il.com" <vinholikatti@...il.com>,
Stanislav Nijnikov <Stanislav.Nijnikov@....com>
CC: "gwendal@...omium.org" <gwendal@...omium.org>
Subject: Re: [PATCH 1/7] scsi: ufs: Add Configuration Descriptor to sysfs
On Tue, 2018-05-29 at 11:17 -0700, Evan Green wrote:
> This change adds the configuration descriptor to the UFS
> sysfs interface. This is done in preparation for making the
> interface writable, which will enable provisioning UFS devices
> via Linux.
>
> The configuration descriptor is laid out as a header, then a set of
> (usually 8) copies of the same descriptor for each unit. Rather than
> creating 8 sets of the same attribute, this interface adds a cfg_unit
> file, which can be set as an index that defines which of the 8
> configuration unit descriptors are being shown through sysfs.
I don't know any other example of a sysfs attribute that controls the
contents of another sysfs attribute so I don't know whether this kind
of behavior is acceptable for sysfs attributes. Additionally, how can
these two sysfs attributes be used together from concurrently running
processes without triggering a race condition?
Bart.
Powered by blists - more mailing lists