> -----Original Message----- > From: Javier González <javier@xxxxxxxxxxx> > Sent: Tuesday, 16 June 2020 17.55 > To: Keith Busch <kbusch@xxxxxxxxxx> > Cc: Damien Le Moal <Damien.LeMoal@xxxxxxx>; Matias Bjørling > <mb@xxxxxxxxxxx>; Jens Axboe <axboe@xxxxxxxxx>; Niklas Cassel > <Niklas.Cassel@xxxxxxx>; Ajay Joshi <Ajay.Joshi@xxxxxxx>; Sagi Grimberg > <sagi@xxxxxxxxxxx>; Keith Busch <Keith.Busch@xxxxxxx>; Dmitry Fomichev > <Dmitry.Fomichev@xxxxxxx>; Aravind Ramesh <Aravind.Ramesh@xxxxxxx>; > linux-nvme@xxxxxxxxxxxxxxxxxxx; linux-block@xxxxxxxxxxxxxxx; Hans Holmberg > <Hans.Holmberg@xxxxxxx>; Christoph Hellwig <hch@xxxxxx>; Matias Bjorling > <Matias.Bjorling@xxxxxxx> > Subject: Re: [PATCH 5/5] nvme: support for zoned namespaces > > On 16.06.2020 08:48, Keith Busch wrote: > >On Tue, Jun 16, 2020 at 05:02:17PM +0200, Javier González wrote: > >> This depends very much on how the FS / application is managing > >> stripping. At the moment our main use case is enabling user-space > >> applications submitting I/Os to raw ZNS devices through the kernel. > >> > >> Can we enable this use case to start with? > > > >I think this already provides that. You can set the nsid value to > >whatever you want in the passthrough interface, so a namespace block > >device is not required to issue I/O to a ZNS namespace from user space. > > Mmmmm. Problem now is that the check on the nvme driver prevents the ZNS > namespace from being initialized. Am I missing something? You can issue the io to the char device (e.g., /dev/nvme0), and specify the namespace. That will be initialized. If you like, you can use Keith's libnvme, that exposes all of the functionality to issue passthru I/Os. Best, Matias
