[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 8 Aug 2017 03:29:52 -0400
From: Keith Busch <keith.busch@...el.com>
To: Sreekanth Reddy <sreekanth.reddy@...adcom.com>
Cc: James Bottomley <James.Bottomley@...senpartnership.com>,
Kashyap Desai <kashyap.desai@...adcom.com>,
Christoph Hellwig <hch@...radead.org>,
Hannes Reinecke <hare@...e.de>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
Chaitra Basappa <chaitra.basappa@...adcom.com>,
Suganath Prabu Subramani
<suganath-prabu.subramani@...adcom.com>,
Sathya Prakash Veerichetty <sathya.prakash@...adcom.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-nvme@...ts.infradead.org,
"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support:
On Tue, Aug 08, 2017 at 12:33:40PM +0530, Sreekanth Reddy wrote:
> On Tue, Aug 8, 2017 at 9:34 AM, Keith Busch <keith.busch@...el.com> wrote:
> >
> > It looks like they can make existing nvme tooling work with little
> > effort if they have the driver implement NVME_IOCTL_ADMIN_COMMAND, and
>
> Precisely, I was thinking on the same line and you clarified. I will
> spend sometime on this and get back to you.
Sounds good. Just note that while the majority of NVMe management should
be reachable with just that IOCTL, some tooling features may not work
correctly since they look for /dev/nvmeX, and I assume this driver will
create /dev/sdX instead.
Powered by blists - more mailing lists