[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <805645c1-ea40-2e57-88eb-5dd34e579b2e@deltatee.com>
Date: Wed, 2 May 2018 09:56:09 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Christian König <christian.koenig@....com>,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-rdma@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-block@...r.kernel.org
Cc: Stephen Bates <sbates@...thlin.com>,
Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Keith Busch <keith.busch@...el.com>,
Sagi Grimberg <sagi@...mberg.me>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Max Gurtovoy <maxg@...lanox.com>,
Dan Williams <dan.j.williams@...el.com>,
Jérôme Glisse <jglisse@...hat.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Alex Williamson <alex.williamson@...hat.com>
Subject: Re: [PATCH v4 00/14] Copy Offload in NVMe Fabrics with P2P PCI Memory
Hi Christian,
On 5/2/2018 5:51 AM, Christian König wrote:
> it would be rather nice to have if you could separate out the functions
> to detect if peer2peer is possible between two devices.
This would essentially be pci_p2pdma_distance() in the existing
patchset. It returns the sum of the distance between a list of clients
and a P2PDMA provider. It returns -1 if peer2peer is not possible
between the devices (presently this means they are not behind the same
root port).
Logan
Powered by blists - more mailing lists