From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8F6661B052 for ; Mon, 8 Jan 2018 16:16:11 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0380620DB0; Mon, 8 Jan 2018 10:16:11 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 08 Jan 2018 10:16:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=WUSyXxXT+mQLT3NQPcPD01XYA5 hrhN343FONV2NGNNI=; b=n/W8l+UdQv3jVMeQ+DpQXfg2aiqRJCqIdOp62YU2fq UaUm6Y0s/0apq7VBVPFsdR8lqU3ZZn8VK2uu5aMFsrW18QvvSMwwtZb+so2yH1zJ CsHz5G3jhetNITgCa47Qoe5KeL/YQlnrq5XXcxY4hKGgy67nsXOffWK8oQTYcOAt M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=WUSyXx XT+mQLT3NQPcPD01XYA5hrhN343FONV2NGNNI=; b=IcrxPIAwDg95UI5FXUb/c8 7sNoLrctsexOLutN1jIJlA3TX4M3bRKMlfg6NGWiozknG5TSJYxjpLtqadKEv+2+ NznF7cqk83x+7YQEQaT3kOMtYdyuT+FE7F+qSk8j4ZlyLadUMxrt8BNiTVwykUHB m4o8u7zW0OrKagr9mButTdgSiMiNncEFaXImlhI+xOHkVNoakk20NlzVWri3MrV+ 4eZSE0pIIhWdKCSQuKoYef4t7Ea6S0U4gjTaQwdsQtMvhl7i/nnEO99rIwhALxm+ dY2r5cufOrWAKWdGN096KnBJ6T2sV+7ZsDLxl2aOcpnZOpgI4ysPuoR3yrcfGwCg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A3B732473E; Mon, 8 Jan 2018 10:16:10 -0500 (EST) From: Thomas Monjalon To: Finn Christensen Cc: dev@dpdk.org Date: Mon, 08 Jan 2018 16:15:47 +0100 Message-ID: <1643500.LyBOxPcb61@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Mon, 08 Jan 2018 15:16:11 -0000 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.