From mboxrd@z Thu Jan 1 00:00:00 1970 From: Finn Christensen Subject: Napatech pmd Date: Mon, 8 Jan 2018 13:08:13 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: Thomas Monjalon Return-path: Received: from mail02.napatech.com (mail02.napatech.com [188.120.77.119]) by dpdk.org (Postfix) with ESMTP id 2EEFA16E for ; Mon, 8 Jan 2018 14:08:15 +0100 (CET) Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Thomas, Thanks for bringing this discussion up again. The Napatech PMD is build on top of our proprietary driver. The reason is b= asically that we utilize many years of driver development and thus reuses t= he FPGA controlling code in the DPDK PMD. The Napatech driver suite is stil= l closed source. The current NTNIC PMD dynamically links a Napatech proprietary NTAPI librar= y 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). Furthermo= re, 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 d= o, therefore we haven't got to that yet. If the DPDK community would accept the dynamic linking to a proprietary lib= rary, from inside our PMD, then it would be great. Let me know what you think. Or maybe you have ideas to what else we could d= o to make it upstream. Thanks, Finn >-----Original Message----- >From: Thomas Monjalon [mailto:thomas@monjalon.net] >Sent: 5. januar 2018 16:34 >To: Finn Christensen >Subject: Re: [dpdk-dev] standardize device identification > >It leads to a totally different question: >Can we discuss again how to integrate your driver in DPDK upstream? >Please explain again your situation in a new thread.