On Thu, Mar 25, 2021 at 12:25:24PM +0000, Niklas Cassel wrote: > On Mon, Mar 01, 2021 at 08:24:51PM +0100, javier@xxxxxxxxxxx wrote: > > From: Javier González <javier.gonz@xxxxxxxxxxx> > > > > Create a char device per NVMe namespace. This char device is always > > initialized, independently of whether the features implemented by the > > device are supported by the kernel. User-space can therefore always > > issue IOCTLs to the NVMe driver using the char device. > > > > The char device is presented as /dev/nvme-generic-XcYnZ. This naming > > scheme follows the convention of the hidden device (nvmeXcYnZ). Support > > for multipath will follow. > > Do we perhaps want to put these new character devices inside a subdir? > e.g. /dev/nvme/nvme-generic-XcYnZ ? I actually suggested the same hierarchy, but that was rejected. > Otherwise it feels like doing such a simple thing as ls -al /dev/nvme* > will show a lot of devices because of these new specialized char devices.
