[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0181dbb9-0b63-5a99-0425-ec77fe5b1e3f@deltatee.com>
Date: Thu, 1 Mar 2018 16:54:51 -0700
From: Logan Gunthorpe <logang@...tatee.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Dan Williams <dan.j.williams@...el.com>
Cc: Jens Axboe <axboe@...nel.dk>, Keith Busch <keith.busch@...el.com>,
Oliver OHalloran <oliveroh@....ibm.com>,
Alex Williamson <alex.williamson@...hat.com>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
linux-rdma <linux-rdma@...r.kernel.org>,
linux-pci@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
Jérôme Glisse <jglisse@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Max Gurtovoy <maxg@...lanox.com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v2 00/10] Copy Offload in NVMe Fabrics with P2P PCI Memory
On 01/03/18 04:26 PM, Benjamin Herrenschmidt wrote:
> The big problem is not the vmemmap, it's the linear mapping.
Ah, yes, ok.
Logan
Powered by blists - more mailing lists