[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190624061617.GA2848@lst.de>
Date: Mon, 24 Jun 2019 08:16:17 +0200
From: Christoph Hellwig <hch@....de>
To: Daniel Drake <drake@...lessm.com>
Cc: Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Keith Busch <kbusch@...nel.org>,
Sagi Grimberg <sagi@...mberg.me>,
linux-nvme <linux-nvme@...ts.infradead.org>,
Linux PCI <linux-pci@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, linux-ide@...r.kernel.org,
Linux Upstreaming Team <linux@...lessm.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Hannes Reinecke <hare@...e.de>,
Alex Williamson <alex.williamson@...hat.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH v2 2/5] nvme: rename "pci" operations to "mmio"
On Thu, Jun 20, 2019 at 04:11:26PM +0800, Daniel Drake wrote:
> On Thu, Jun 20, 2019 at 2:11 PM Christoph Hellwig <hch@....de> wrote:
> > The Linux NVMe driver will deal with NVMe as specified plus whatever
> > minor tweaks we'll need for small bugs. Hiding it behind an AHCI
> > device is completely out of scope and will not be accepted.
>
> Do you have any new suggestions for alternative ways we can implement
> support for this storage configuration?
IFF we want to support it it has to be done at the PCIe layer. But
even that will require actual documentation and support from Intel.
If Intel still believes this scheme is their magic secret to control
the NVMe market and give themselves and unfair advantage over their
competitors there is not much we can do.
Powered by blists - more mailing lists