[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200819214248.GA26769@dhcp-10-100-145-180.wdl.wdc.com>
Date: Wed, 19 Aug 2020 14:42:48 -0700
From: Keith Busch <kbusch@...nel.org>
To: David Fugate <david.fugate@...ux.intel.com>
Cc: Christoph Hellwig <hch@....de>,
Kanchan Joshi <joshi.k@...sung.com>,
"Damien.LeMoal@....com" <Damien.LeMoal@....com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"johannes.thumshirn@....com" <johannes.thumshirn@....com>,
Nitesh Shetty <nj.shetty@...sung.com>,
SelvaKumar S <selvakuma.s1@...sung.com>,
Javier Gonzalez <javier.gonz@...sung.com>
Subject: Re: [PATCH 2/2] nvme: add emulation for zone-append
On Wed, Aug 19, 2020 at 01:11:58PM -0600, David Fugate wrote:
> Intel does not support making *optional* NVMe spec features *required*
> by the NVMe driver.
This is inaccurate. As another example, the spec optionally allows a
zone size to be a power of 2, but linux requires a power of 2 if you
want to use it with this driver.
> Provided there's no glaring technical issues
There are many. Some may be improved through a serious review process,
but the mess it makes out of the fast path is measurably harmful to
devices that don't subscribe to this. That issue is not so easily
remedied.
Since this patch is a copy of the scsi implementation, the reasonable
thing is take this fight to the generic block layer for a common
solution. We're not taking this in the nvme driver.
Powered by blists - more mailing lists