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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200728211427.GA22919@lst.de>
Date:   Tue, 28 Jul 2020 23:14:27 +0200
From:   Christoph Hellwig <hch@....de>
To:     Jonathan Lemon <jonathan.lemon@...il.com>
Cc:     Jason Gunthorpe <jgg@...dia.com>, Christoph Hellwig <hch@....de>,
        netdev@...r.kernel.org, kernel-team@...com, robin.murphy@....com,
        akpm@...ux-foundation.org, davem@...emloft.net, kuba@...nel.org,
        willemb@...gle.com, edumazet@...gle.com,
        steffen.klassert@...unet.com, saeedm@...lanox.com,
        maximmi@...lanox.com, bjorn.topel@...el.com,
        magnus.karlsson@...el.com, borisp@...lanox.com, david@...hat.com
Subject: Re: [RFC PATCH v2 21/21] netgpu/nvidia: add Nvidia plugin for
 netgpu

On Tue, Jul 28, 2020 at 02:01:16PM -0700, Jonathan Lemon wrote:
> For /this/ patch [21], this is quite true.  I'm forced to use the nv_p2p
> API if I want to use the hardware that I have.  What's being overlooked
> is that the host mem driver does not do this, nor would another GPU
> if it used p2p_dma.  I'm just providing get_page, put_page, get_dma.

No, that is not overlooked.   What you overlooked is that your design
is bogus.  We don't do pointless plugings for something where there
is exactly one way to do, which is done in common infrastructure.

> 
> 
> > Any approach done in tree, where we can actually modify the GPU
> > driver, would do sane things like have the GPU driver itself create
> > the MEMORY_DEVICE_PCI_P2PDMA pages, use the P2P DMA API framework, use
> > dmabuf for the cross-driver attachment, etc, etc.
> 
> So why doesn't Nvidia implement the above in the driver?
> Actually a serious question, not trolling here.

No one knows, and most importantly it simply does not matter at all.

If you actually want to be productive contributor and not just troll
(as it absoutely seems) you'd just stop talking about a out of tree
driver that can't actually be distributed together with the kernel.

And better forget everything you ever knew about it, because it not
only is irrelevant but actually harmful.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ