From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD22AC433E4 for ; Tue, 28 Jul 2020 21:14:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C121220768 for ; Tue, 28 Jul 2020 21:14:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729379AbgG1VOc (ORCPT ); Tue, 28 Jul 2020 17:14:32 -0400 Received: from verein.lst.de ([213.95.11.211]:50006 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729363AbgG1VOc (ORCPT ); Tue, 28 Jul 2020 17:14:32 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 90DCB68C4E; Tue, 28 Jul 2020 23:14:27 +0200 (CEST) Date: Tue, 28 Jul 2020 23:14:27 +0200 From: Christoph Hellwig To: Jonathan Lemon Cc: Jason Gunthorpe , Christoph Hellwig , netdev@vger.kernel.org, kernel-team@fb.com, robin.murphy@arm.com, akpm@linux-foundation.org, davem@davemloft.net, kuba@kernel.org, willemb@google.com, edumazet@google.com, steffen.klassert@secunet.com, saeedm@mellanox.com, maximmi@mellanox.com, bjorn.topel@intel.com, magnus.karlsson@intel.com, borisp@mellanox.com, david@redhat.com Subject: Re: [RFC PATCH v2 21/21] netgpu/nvidia: add Nvidia plugin for netgpu Message-ID: <20200728211427.GA22919@lst.de> References: <20200727052846.4070247-1-jonathan.lemon@gmail.com> <20200727052846.4070247-22-jonathan.lemon@gmail.com> <20200727073509.GB3917@lst.de> <20200727170003.clx5ytf7vn2emhvl@bsd-mbp.dhcp.thefacebook.com> <20200727182424.GA10178@lst.de> <20200728014812.izihmnon3khzyr32@bsd-mbp.dhcp.thefacebook.com> <20200728181904.GA138520@nvidia.com> <20200728210116.56potw45eyptmlc7@bsd-mbp.dhcp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200728210116.56potw45eyptmlc7@bsd-mbp.dhcp.thefacebook.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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.