linux-kernel - Re: [PATCH v6 06/13] PCI/P2PDMA: Add P2P DMA driver writer's documentation

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180921194700.GM224714@bhelgaas-glaptop.roam.corp.google.com>
Date:   Fri, 21 Sep 2018 14:47:00 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Logan Gunthorpe <logang@...tatee.com>
Cc:     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,
        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>,
        Jens Axboe <axboe@...nel.dk>, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v6 06/13] PCI/P2PDMA: Add P2P DMA driver writer's
 documentation

On Fri, Sep 21, 2018 at 12:03:12PM -0600, Logan Gunthorpe wrote:
> On 2018-09-21 10:41 AM, Bjorn Helgaas wrote:
> >> +away, the one returned will be chosen at random. This function returns the PCI
> > 
> > s/the one returned will be chosen at random/one will be chosen
> > arbitrarily/ ?  (I doubt it's really random)
> 
> You're the second person to ask this, but yes, we really do it randomly.
> Such that if there are multiple drivers getting resources they should be
> evenly distributed. It's not the ideal solution but if it were to do it
> arbitrarily then the code would likely return the same device all the
> time and any additional devices would not get used.

Ah, I see, I should have searched for "random" in that patch and answered
my own question :)  Sorry for the noise.

Bjorn