From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] ntnic: add PMD driver Date: Sat, 27 Aug 2016 11:07:17 +0200 Message-ID: <1508379.3KBpzu8YCG@xps13> References: <20160826134401.19337-1-fc@napatech.com> <4874006.xIzEWfahEa@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Finn Christensen Return-path: Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id 1DBEC4B79 for ; Sat, 27 Aug 2016 11:07:19 +0200 (CEST) Received: by mail-wm0-f42.google.com with SMTP id o80so22793840wme.1 for ; Sat, 27 Aug 2016 02:07:19 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-08-26 16:32, Finn Christensen: > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > It would help a lot to describe what is the Napatech NIC Driver Suite, and > > why it is a virtual driver. > > I will elaborate on the description to make it more clear and send an update > patch. However, the driver is a virtual driver because we already bypasses > the kernel stack in our NIC driver and does that in an effective manner. Is there some plan to upstream your driver in Linux? We need to think about the limitations we could have when implementing a PCI driver as a virtual driver. Any thoughts? [...] > > Where can we download the Driver Suite? > > When the Napatech NIC is released, the driver suite will then be available for download. > If you need something sooner, we will need to make special arrangements. We cannot accept a driver until we can freely compile it. What is the expected release date?