From: Neil Horman <nhorman@tuxdriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Michael Lilja <ml@napatech.com>,
Thomas Monjalon <thomas@monjalon.net>,
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: Tue, 31 Mar 2020 15:51:37 -0400 [thread overview]
Message-ID: <20200331195137.GB3858830@hmswarspite.think-freely.org> (raw)
In-Reply-To: <20200331075845.28c3d4e3@hermes.lan>
On Tue, Mar 31, 2020 at 07:58:45AM -0700, Stephen Hemminger wrote:
> On Tue, 31 Mar 2020 12:39:17 +0000
> Michael Lilja <ml@napatech.com> wrote:
>
> > Hi,
> >
> > I appreciate the discussion. It would of course be nice if vendors could be allowed to use external libraries/drivers and have a DPDK shim but I also understand the concern.
> >
> > We have started the movement towards an open source variant of our NICs driver so that upstreaming to DPDK (and kernel) will be possible. The downside is that not all NICs will be supported, it is simply not worth the effort rewriting a legacy codebase.
> >
> > Thanks,
> > Michael
>
> The downside is that any proprietary requirement means code is untestable by
> any CI or infrastructure. Therefore it is likely to be broken.
>
This. This is exactly my concern. Because the Napatech PMD is really just an
interface to some proprietary code, no one outside of Napatech will have any
insight or ability to test (or use) it.
next prev parent reply other threads:[~2020-03-31 19:51 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 [this message]
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
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=20200331195137.GB3858830@hmswarspite.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=bk@napatech.com \
--cc=dev@dpdk.org \
--cc=fc@napatech.com \
--cc=ml@napatech.com \
--cc=stephen@networkplumber.org \
--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).