From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 374431B170 for ; Tue, 9 Jan 2018 21:20:49 +0100 (CET) Received: from cpe-2606-a000-111b-423c-e874-da8e-c543-d863.dyn6.twc.com ([2606:a000:111b:423c:e874:da8e:c543:d863] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1eZ0O3-0001Ib-Dz; Tue, 09 Jan 2018 15:20:46 -0500 Date: Tue, 9 Jan 2018 15:20:06 -0500 From: Neil Horman To: Michael Lilja Cc: "dev@dpdk.org" , Finn Christensen , Thomas Monjalon Message-ID: <20180109202006.GC14094@hmswarspite.think-freely.org> References: <1643500.LyBOxPcb61@xps> <20180109185037.GB14094@hmswarspite.think-freely.org> <82be0f1b54b543ed8f7bf0799512b1cd@napatech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <82be0f1b54b543ed8f7bf0799512b1cd@napatech.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: Re: [dpdk-dev] Napatech pmd X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 20:20:49 -0000 On Tue, Jan 09, 2018 at 07:57:50PM +0000, Michael Lilja wrote: > > On Mon, Jan 08, 2018 at 04:15:47PM +0100, Thomas Monjalon wrote: > > > Hi, > > > > > > 08/01/2018 14:08, Finn Christensen: > > > > Hi Thomas, > > > > > > > > Thanks for bringing this discussion up again. > > > > > > > > The Napatech PMD is build on top of our proprietary driver. The > > reason is basically that we utilize many years of driver development and > > thus reuses the FPGA controlling code in the DPDK PMD. The Napatech > > driver suite is still closed source. > > > > The current NTNIC PMD dynamically links a Napatech proprietary > > NTAPI library to control the FPGA on our NICs. > > > > > > > > We did think of the PMD as being our responsibility to keep updated > > towards the Napatech NIC communication, and that we would be > > engaged and asked to modify accordingly if changes in DPDK required > > that (maintainer). Furthermore, the PMD compiles with no issues, when > > NTNIC is enabled. > > > > We have plans to write a stand-alone PMD, but this is not a small task > > to do, therefore we haven't got to that yet. > > > > > > This standalone PMD would be open and BSD licensed? > > > > > > > If the DPDK community would accept the dynamic linking to a > > proprietary library, from inside our PMD, then it would be great. > > > > > > Dynamic linking is OK. > > > I think we can accept such PMD at the condition that we can build it, > > > meaning we can easily download the build dependencies for free. > > > > > > > Let me know what you think. Or maybe you have ideas to what else > > we could do to make it upstream. > > > > > > My thinking is to allow every hardware to have a good DPDK support. > > > Every step in this direction is a progress. > > > > > > > I have to ask the question: Why not open source your FPGA code? That > > would make all of this a non issue. > > > > While I knows it to various degrees been done in the past, I really don't > > like the idea of including drivers (even open source drivers), if they have > > dependencies on closed source software. It means that we as a > > community assume some level of responsibility for that pmd, but have > > no ability to make fixes to that pmd without accepting your license > > terms. I understand that you are saying you currently have responsibility > > for it as the license owner, but if that chages in the future, the PMD has > > no use to the community. It would be preferable if access to controlling > > the hardware was just free of a proprietary license. Then you wouldn't > > have to write a stand alone pmd. > > > > Neil > I understand your concern, but it is quite normal that BSP (Board Support Package) is binary and has an API that is BSD licensed. The Napatech Suite is basically a BSP. The API that will be used in the PMD is a BSD licensed API and so will the PMD be. If you understand the API you will be able to control the hardware and thereby also be able to change the DPDK driver. The API is public available and so is the BSP binary package. A good analogy is how Android does open source develop for Quallcomm based HW boards, where the Quallcomm firmware is proprietary. Any user can download full Android stack and BSP packages free of charge to do Android development. > > /Michael > You can couch it any way you like, but regardless of how you want to view the proprietary part of this system, the hardware is being used as a NIC in the DPDK, and for that purpose you need a driver. As you currently have it architected, the driver (open source or not), is useless without the binary portion underneath it, and so is useless to any user without agreeing to your license terms. Pert of the benefit of open source software is that users can continue to modify/enchance/maintain the software powering your hardware after you decide to stop supporting it. And so I'm not comfortable with accepting code that doesn't allow this community to do that. Neil > > > Disclaimer: This email and any files transmitted with it may contain confidential information intended for the addressee(s) only. The information is not to be surrendered or copied to unauthorized persons. If you have received this communication in error, please notify the sender immediately and delete this e-mail from your system. >