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 69BD52BB3 for ; Mon, 29 Aug 2016 08:22:42 +0200 (CEST) IronPort-PHdr: 9a23:bJm7bBXX4htMkbDvjHPxdfXDyEnV8LGtZVwlr6E/grcLSJyIuqrYZxSBt8tkgFKBZ4jH8fUM07OQ6PG5HzBbqsze6DhCKMUKDE5dz51O3kQJO42sMQXDNvnkbig3ToxpdWRO2DWFC3VTA9v0fFbIo3e/vnY4ExT7MhdpdKyuQtaBx/q+2+36wZDPeQIA3GP7OuIraknt5l+O7oFW2dIkcfdpjEOR4zNhQKd//StQP1WdnhLxtI+b3aVI1GBugc8n7NNKSq7gfq41HvRyBTUiNH0ptoWw7UGQBSPG3HYXU30XnxxUGECFqUiiBtai+hf949Fh1TGaMMu+bb0xXDWk4KpxAEvzlCofNzM/2GfaltN3lqFDpA+krRFlhYnOb9fGGuB5e/bzfNUcDUFBRMdKSyFHGY66J98BBMIHNP5Rs4T2px0Fqh7oVlrkP//m1jId3iy+5qY9yel0VFiehAE= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2G0AQBf1MNX/1QB8ApdGgEBAQECAQEBARUBAQEBAgEBAQGDCgEBAQEBHoFTB40nqGeCD4IBgmaDNwKBNDgUAQEBAQEBAQEBAQECWyeCMgQBFQEEghABAQEBAgE6PwULAgEFAxEEAQEBHgkHMhQJCAIEDgUIE4gdDL0fAQEBAQEBAQEBAQEBAQEBAQEBH4YuhE2EEhEBhXgFiCaHNYl0jySBdIRdgzSFV4xEg3keNoI0HIFMPDSELV9BAX4BAQE X-IPAS-Result: A2G0AQBf1MNX/1QB8ApdGgEBAQECAQEBARUBAQEBAgEBAQGDCgEBAQEBHoFTB40nqGeCD4IBgmaDNwKBNDgUAQEBAQEBAQEBAQECWyeCMgQBFQEEghABAQEBAgE6PwULAgEFAxEEAQEBHgkHMhQJCAIEDgUIE4gdDL0fAQEBAQEBAQEBAQEBAQEBAQEBH4YuhE2EEhEBhXgFiCaHNYl0jySBdIRdgzSFV4xEg3keNoI0HIFMPDSELV9BAX4BAQE 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 08:22:37 +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 08:22:37 +0200 From: Finn Christensen To: Stephen Hemminger CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] ntnic: add PMD driver Thread-Index: AQHR/6A1UIRSrvjC10Otwgv4WiQgL6BbVCWAgAGIe/A= Date: Mon, 29 Aug 2016 06:22:37 +0000 Message-ID: <8cec6b8c3d6c4a7f85ac117d2d90fd7e@napatech.com> References: <20160826134401.19337-1-fc@napatech.com> <20160826095409.6d49a24a@xeon-e3> In-Reply-To: <20160826095409.6d49a24a@xeon-e3> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [83.93.6.59] 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 06:22:43 -0000 > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: 26. august 2016 18:54 > To: Finn Christensen > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] ntnic: add PMD driver > > On Fri, 26 Aug 2016 13:44:01 +0000 > Finn Christensen wrote: > > > +The NTNIC poll mode driver library (**librte_pmd_ntnic**) implements > > +support for **Napatech NIC** 40/50 Gbps adapters. > > +This PMD is implemented as a pure software virtual device and must be > > +created by using the EAL --vdev=3Dparameter (parameters are explained = i > detail later). > > +It runs on top of the Napatech NIC Driver Suite that must be > > +installed and started. > > What is the license of this driver suite? The driver suite is a closed-source driver, which is not free downloadable. > 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 bypa= sses the kernel effectively in our driver, this first solution for a DPDK P= MD driver, has been built on top of that software suite. We like the idea of opensource, but we will need to do the transition stepw= ise, considering our NIC product. We have seen large performance improvements (x4-x7 times with 64 byte packe= ts 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 c= ontribution 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. We ma= y need to make that possible, so that a free downloadable driver can be ret= rieved. Once this is said, we thought that the DPDK was BSD licensed and I must adm= it that we have failed to see this limitation that you are mentioning. Is t= here another license or agreement text that we need to read? Thanks for your repy! 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.