From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A0D41A0588; Fri, 17 Apr 2020 06:38:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 22A471DDCF; Fri, 17 Apr 2020 06:38:55 +0200 (CEST) Received: from mail02.napatech.com (mail02.napatech.com [188.120.77.119]) by dpdk.org (Postfix) with ESMTP id 00F421DD8D; Fri, 17 Apr 2020 06:38:53 +0200 (CEST) Received: from mail02.napatech.com (localhost [127.0.0.1]) by mail02.napatech.com (Postfix) with ESMTP id C027B9CC99; Fri, 17 Apr 2020 06:38:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=napatech.com; s=mar2017; t=1587098331; bh=7MKhzn0ckAu7hXMNSD5e6EflXB12d/sEGClc/wkbCks=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=lH0n2r9pcM2bh4rzZydrjjzzRcDNhj3QXWpXAR7ks7nlLS4RkVFuB5S2H8ES3Rge6 I0un+Ta+EAaUnwZY/G5Rq3Vo2zkEgHDP1YQKRO30UiCA+Fx+jryaV1Q1WYt/xit2me LTJ8KLM6dy1phkXUy+IIQNjngNIMKc0fj1modJJLusBEFkXNUXI3RbRXJlt8YkAOq4 P0SPAO94DrW2CV2KpdTMJJfJAjaoE5BkU4KaBGfD5krp8MnPCjfbbF2J9tynLn1Vx4 rzUMwusWgTi8vJu5DsLLDWDlmL8N5oOisRICa8oVmUGTHoqFld6GMIXwzYZ1+D3kLN emTFjxiAZa04Q== Received: from localhost (localhost [127.0.0.1]) by mail02.napatech.com (Postfix) with ESMTP id BD21B9CC98; Fri, 17 Apr 2020 06:38:51 +0200 (CEST) X-Virus-Scanned: by SpamTitan at napatech.com Received: from mail02.napatech.com (localhost [127.0.0.1]) by mail02.napatech.com (Postfix) with ESMTP id 186809CC9D; Fri, 17 Apr 2020 06:38:49 +0200 (CEST) Authentication-Results: mail02.napatech.com; none Received: from mail.napatech.com (cph-gen-exch02.napatech.com [10.240.1.84]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail02.napatech.com (Postfix) with ESMTPS id 845659CC9A; Fri, 17 Apr 2020 06:38:46 +0200 (CEST) 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 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 17 Apr 2020 06:38:42 +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.1913.005; Fri, 17 Apr 2020 06:38:42 +0200 From: Michael Lilja To: Neil Horman , Thomas Monjalon CC: Finn Christensen , "dev@dpdk.org" , "Bent Kuhre" , "techboard@dpdk.org" Thread-Topic: [dpdk-dev] Napatech pmd Thread-Index: AQHWB1gAjoqbSs4S00yV0CaMaRpMEahi/NeAgAAC3wCAGZc6gIAAPGVQ Date: Fri, 17 Apr 2020 04:38:42 +0000 Message-ID: References: <11835288.hYdu0Ggh8K@xps> <20200331195655.GC3858830@hmswarspite.think-freely.org> <4836428.jY9Djz4Zq0@xps> <20200417025457.h4uqif7qtjfb2x2q@penguin.lxd> In-Reply-To: <20200417025457.h4uqif7qtjfb2x2q@penguin.lxd> Accept-Language: en-US, da-DK, de-DE, de-CH, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [188.177.108.27] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Neil Horman > Sent: 17. april 2020 04:55 > To: Thomas Monjalon > Cc: Finn Christensen ; dev@dpdk.org; Bent Kuhre > ; Michael Lilja ; techboard@dpdk.org > Subject: Re: [dpdk-dev] Napatech pmd >=20 > On Tue, Mar 31, 2020 at 10:07:12PM +0200, Thomas Monjalon wrote: > > 31/03/2020 21:56, Neil Horman: > > > On Tue, Mar 31, 2020 at 02:29:08PM +0200, Thomas Monjalon wrote: > > > > 31/03/2020 14:17, Neil Horman: > > > > > On Tue, Mar 31, 2020 at 01:25:25PM +0200, Thomas Monjalon > wrote: > > > > > > Hi, > > > > > > > > > > > > Raising this topic again. > > > > > > > > > > > > As said in the past, it is better to have this PMD inside > DPDK. > > > > > > We discussed some concerns, but I think the consensus was to > > > > > > integrate Napatech PMD anyway. > > > > > > > > > > > > I am sad that you did not feel welcome enough to follow up > > > > > > with patches during all these years. > > > > > > Please would you like to restart the upstreaming process? > > > > > > > > > > > Whats changed here? > > > > > > > > Nothing changed, except years. > > > > > > > > > I still don't see what the advantage is to accepting this code > in the DPDK tree. > > > > > No one will be able to use it without accepting Napatechs > > > > > license for their underlying library. As such, the code can't > > > > > really be maintained at all by anyone other than Napatech in > the > > > > > community, and so may as well just be maintained as an out of > tree driver. > > > > > > > > You are the only one having this concern. > > > I don't think its wise to assume that silence implies acceptance. > > > > > > > Nobody from the Technical Board looks to be against the > acceptance. > > > > > > > > The advantage is simple: Napatech customers will be able to run > any DPDK version. > > > Why is that not possible by having napatech maintain an out-of- > tree > > > PMD? Theres no reason that can't be done. > > > > They are maintaining an out-of-tree PMD: > > https://github.com/napatech/dpdk/releases > > > > I'm just trying to improve the situation, avoiding DPDK forks. > > > > > > > Apologies, I completely missed responding to this note >=20 > I took a look at the PMD above. Its not an open source implementation > of their driver, its the same thing they offered 4 years ago, a > skeleton pmd that still uses the same closed licensed library. >=20 > It was my understanding that they were working on a completely open > sourced PMD that could be generally useful to the community. If that > exists, then yes, by all means, lets take a look at it, and consider > merging it. That effort deserves consideration. >=20 > This however, is the same thing we saw last time. Theres no benefit > in including that >=20 > Neil I understand the confusion. The PMD in our github is still, as you correctl= y state, based on our closed source driver and only a skeleton. We are work= ing on a open source version, but currently that is WIP and not pushed yet.= I'll let you know when there is something to look at. Michael