From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.napatech.com (mail02.napatech.com [91.102.88.21]) by dpdk.org (Postfix) with ESMTP id 5248111C5 for ; Mon, 29 Aug 2016 14:00:13 +0200 (CEST) IronPort-PHdr: 9a23:ctKacBRW8wefRm46e9lm4GxD29psv+yvbD5Q0YIujvd0So/mwa65ZBWN2/xhgRfzUJnB7Loc0qyN4vmmBTBLvc3J8ChbNscdD1ld0YRetjdjKfbNMVf8Iv/uYn5yN+V5f3ghwUuGN1NIEt31fVzYry76xzcTHhLiKVg9fbytScbshsi6n9q/54fUK10RwmHsOPUucF7q9k2R7pBQ2to6bP5pi1PgmThhQ6xu32RmJFaezV7Xx/yb29pdyRlWoO8r7MVaUK/3LOwSRL1cCyk6YShuvJW4/TGKdwaE52MdX2MKiVIIRlGdtFCpFqv25xf6se90w2G/Osv0RLQzX3z286dsTRbzziIAMTww9GbRopJvjaRX5hmmokos7ZTTZdS7Nfx4NojdZ9IBWWdHRctXH3hPCau6ZpMGE+cKPaBTqIyr9AhGlge3GQT5XLCn8TRPnHKjmPRii+k= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2FSAQBTIMRX/1QB8ApcGgEBAQECAQEBARUBAQEBAgEBAQGDCgEBAQEBgXEHjSeoaIIPggGCZoM3AoF7FAEBAQEBAQEBAQEBAoECgjIEARUBBIIQAQEBAQIBOj8FCwIBCBEEAQEfCQcyFAkIAgQOBQgTiB29RAEBAQEBAQEBAQEBAQEBAQEBAR+GLoRNhBIRAYV4BYgmhzWJdI8kgXSEXYM0hVeMRIN5HoJqHIFMcIQtX0F/AQEB X-IPAS-Result: A2FSAQBTIMRX/1QB8ApcGgEBAQECAQEBARUBAQEBAgEBAQGDCgEBAQEBgXEHjSeoaIIPggGCZoM3AoF7FAEBAQEBAQEBAQEBAoECgjIEARUBBIIQAQEBAQIBOj8FCwIBCBEEAQEfCQcyFAkIAgQOBQgTiB29RAEBAQEBAQEBAQEBAQEBAQEBAR+GLoRNhBIRAYV4BYgmhzWJdI8kgXSEXYM0hVeMRIN5HoJqHIFMcIQtX0F/AQEB Received: from cph-gen-exch02.napatech.com (10.240.1.84) by cph-gen-exch02.napatech.com (10.240.1.84) with Microsoft SMTP Server (TLS) id 15.1.396.30; Mon, 29 Aug 2016 14:00:08 +0200 Received: from cph-gen-exch02.napatech.com ([fe80::581:51a1:ac3f:84e]) by cph-gen-exch02.napatech.com ([fe80::581:51a1:ac3f:84e%12]) with mapi id 15.01.0396.030; Mon, 29 Aug 2016 14:00:08 +0200 From: Finn Christensen To: Thomas Monjalon CC: "dev@dpdk.org" , Stephen Hemminger Thread-Topic: [dpdk-dev] [PATCH] ntnic: add PMD driver Thread-Index: AQHR/6A1UIRSrvjC10Otwgv4WiQgL6BbVCWAgAGIe/CAArv5gIAAP86A Date: Mon, 29 Aug 2016 12:00:08 +0000 Message-ID: <02bbac6ecea04602a8ae8dce82d6dc96@napatech.com> References: <20160826134401.19337-1-fc@napatech.com> <20160826095409.6d49a24a@xeon-e3> <8cec6b8c3d6c4a7f85ac117d2d90fd7e@napatech.com> <5255275.7GO0ucYScp@xps13> In-Reply-To: <5255275.7GO0ucYScp@xps13> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.240.10.179] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] ntnic: add PMD driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2016 12:00:13 -0000 > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: 29. august 2016 12:04 > To: Finn Christensen > Cc: dev@dpdk.org; Stephen Hemminger > Subject: Re: [dpdk-dev] [PATCH] ntnic: add PMD driver > > 2016-08-29 06:22, Finn Christensen: > > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > > > What is the license of this driver suite? > > > > The driver suite is a closed-source driver, which is not free downloada= ble. > > > > > IMHO the upstream DPDK shouldn't be a platform for non-free driver > suites. > > > > This is our first steps towards opensource, and our upcoming NIC is > > partly build on HW and SW from our Accelerator products. > > And since we already bypasses the kernel effectively in our driver, > > this first solution for a DPDK PMD driver, has been built on top of > > that software suite. > > We like the idea of opensource, but we will need to do the transition > > stepwise, considering our NIC product. > > I think the first step should be to free the lowest level, here the code = you > build your drivers on. I think that will not become a problem. > > We have seen large performance improvements (x4-x7 times with 64 byte > > packets compared to a std NIC in a phy-ovs-vm-ovs-phy setup utilizing > > a modified DPDK), and this is the main motivation to go forward and > > try to push our contribution to DPDK upstream. > > This is the first step of contributions that we want to make. > > This DPDK PMD solution is not compileable unless you have our driver. > > Not being able to compile the PMD is a real problem for maintenance. > The PMD would be considered as dead code, so is forbidden. Yes, that does fully make sense. We will come up with a way to freely downl= oad a driver with header files and libraries to make it possible for anyone to bu= ild the PMD. > > > We may need to make that possible, so that a free downloadable driver > > can be retrieved. > > > > Once this is said, we thought that the DPDK was BSD licensed and I > > must admit that we have failed to see this limitation that you are > mentioning. > > Is there another license or agreement text that we need to read? > > Maybe you'll find some interesting parts in the contributing guide. > But honestly, I think you have already done the right thing in your case: > you sent some code and open the discussion :) Now you just need to enable > a free compilation environment for your patch. > Thanks We will do that. I'll get back with an updated patch once this has been est= ablished. Thank you both for your help on this. Disclaimer: This email and any files transmitted with it may contain confid= ential information intended for the addressee(s) only. The information is n= ot to be surrendered or copied to unauthorized persons. If you have receive= d this communication in error, please notify the sender immediately and del= ete this e-mail from your system.