DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Lilja <ml@napatech.com>
To: Neil Horman <nhorman@tuxdriver.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: Finn Christensen <fc@napatech.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Bent Kuhre" <bk@napatech.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] Napatech pmd
Date: Fri, 17 Apr 2020 04:38:42 +0000	[thread overview]
Message-ID: <a897c93ae61b4eaabfd3ded63fc9a83b@napatech.com> (raw)
In-Reply-To: <20200417025457.h4uqif7qtjfb2x2q@penguin.lxd>

> -----Original Message-----
> From: Neil Horman <nhorman@tuxdriver.com>
> Sent: 17. april 2020 04:55
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: Finn Christensen <fc@napatech.com>; dev@dpdk.org; Bent Kuhre
> <bk@napatech.com>; Michael Lilja <ml@napatech.com>; techboard@dpdk.org
> Subject: Re: [dpdk-dev] Napatech pmd
> 
> 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
> 
> 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.
> 
> 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.
> 
> This however, is the same thing we saw last time.  Theres no benefit
> in including that
> 
> Neil
I understand the confusion. The PMD in our github is still, as you correctly state, based on our closed source driver and only a skeleton. We are working 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


  reply	other threads:[~2020-04-17  4:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 13:08 Finn Christensen
2018-01-08 15:15 ` Thomas Monjalon
2018-01-08 15:31   ` Stephen Hemminger
2018-01-09 10:43   ` Finn Christensen
2018-01-09 18:50   ` Neil Horman
2018-01-09 19:57     ` Michael Lilja
2018-01-09 20:20       ` Neil Horman
2018-01-09 20:36         ` Thomas Monjalon
2018-01-09 21:21           ` [dpdk-dev] [dpdk-techboard] " Stephen Hemminger
2018-01-10  0:24             ` Neil Horman
2018-01-10 10:21               ` Bruce Richardson
2018-01-10 12:28                 ` Neil Horman
2018-01-10  0:19           ` [dpdk-dev] " Neil Horman
2018-01-10  0:25             ` Thomas Monjalon
2020-03-31 11:25 ` Thomas Monjalon
2020-03-31 12:17   ` Neil Horman
2020-03-31 12:29     ` Thomas Monjalon
2020-03-31 12:39       ` Michael Lilja
2020-03-31 12:45         ` Thomas Monjalon
2020-03-31 13:08           ` Michael Lilja
2020-03-31 14:58         ` Stephen Hemminger
2020-03-31 19:51           ` Neil Horman
2020-03-31 19:59             ` Thomas Monjalon
2020-04-01 12:40               ` Neil Horman
2020-03-31 19:56       ` Neil Horman
2020-03-31 20:07         ` Thomas Monjalon
2020-04-01 12:49           ` Neil Horman
2020-04-17  2:54           ` Neil Horman
2020-04-17  4:38             ` Michael Lilja [this message]
2020-04-19 21:16               ` Neil Horman
2020-04-20  5:05                 ` Michael Lilja
2020-12-11  8:36                   ` Thomas Monjalon
2020-12-11  8:41                     ` Michael Lilja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a897c93ae61b4eaabfd3ded63fc9a83b@napatech.com \
    --to=ml@napatech.com \
    --cc=bk@napatech.com \
    --cc=dev@dpdk.org \
    --cc=fc@napatech.com \
    --cc=nhorman@tuxdriver.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).