lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 31 Aug 2018 09:44:53 -0600 From: Logan Gunthorpe <logang@...tatee.com> To: Randy Dunlap <rdunlap@...radead.org>, 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>, 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>, Christian König <christian.koenig@....com>, Jonathan Corbet <corbet@....net> Subject: Re: [PATCH v5 06/13] PCI/P2PDMA: Add P2P DMA driver writer's documentation Hey, Thanks for the review. I'll make the fixes for the next version. On 30/08/18 06:34 PM, Randy Dunlap wrote: >> +With the client list in hand, the orchestrator may then call> +:c:func:`pci_p2pmem_find()` to obtain a published P2P memory provider >> +that is supported (behind the same root port) as all the clients. If more >> +than one provider is supported, the one nearest to all the clients will >> +be chosen first. If there are more than one provider is an equal distance >> +away, the one returned will be chosen at random. This function returns the PCI > > random or just arbitrarily? Randomly. See pci_p2pmem_find() in patch 1. We use prandom_u32_max() to select any of the supported devices. Logan
Powered by blists - more mailing lists