From: Michael Lilja <ml@napatech.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Finn Christensen <fc@napatech.com>, "dev@dpdk.org" <dev@dpdk.org>,
Bent Kuhre <bk@napatech.com>
Subject: Re: [dpdk-dev] Napatech pmd
Date: Tue, 31 Mar 2020 13:08:01 +0000 [thread overview]
Message-ID: <b25c38b2cdc447f189d3ff343b8be958@napatech.com> (raw)
In-Reply-To: <3804560.zXnORWrf4K@xps>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 31. marts 2020 14:45
> To: Michael Lilja <ml@napatech.com>
> Cc: Neil Horman <nhorman@tuxdriver.com>; Finn Christensen
> <fc@napatech.com>; dev@dpdk.org; Bent Kuhre <bk@napatech.com>
> Subject: Re: [dpdk-dev] Napatech pmd
>
> 31/03/2020 14:39, Michael Lilja:
> > 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.
>
> That's a very good news!
> When do you plan to start upstreaming?
That is a good question... Soon hopefully, it is a work in progress :D
>
>
next prev parent reply other threads:[~2020-03-31 13:08 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 [this message]
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
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=b25c38b2cdc447f189d3ff343b8be958@napatech.com \
--to=ml@napatech.com \
--cc=bk@napatech.com \
--cc=dev@dpdk.org \
--cc=fc@napatech.com \
--cc=nhorman@tuxdriver.com \
--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).