From: Finn Christensen <fc@napatech.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH v3] ntnic: add PMD driver
Date: Mon, 12 Sep 2016 08:08:44 +0000 [thread overview]
Message-ID: <e2f0ee6c4d404108b9de30a4e8efafd2@napatech.com> (raw)
In-Reply-To: <CAOaVG17qeHJQOx5Go07AFMjuxM9KcNRSEDgHYeaDKui9u7E6cw@mail.gmail.com>
Yes, this we can do without asking you guys, and we already do so. But that is not what this ntnic PMD is about.
We have built a NT NIC out of our existing accelerator products. This NIC is built using an FPGA and is targeted towards NFV acceleration in virtualized environments. Now, we have seen good acceleration results in our tests by using DPDK (with small additions to DPDK). What we want to do is to make this part of open source DPDK and in general run this project in an open source spirit.
We want to make further RFCs to the DPDK community about extensions to the DPDK that can accelerate packet processing, and this ntnic PMD is the first step in our participation/contribution into the DPDK project.
Furthermore, we do not think in proprietary code with this project, and no further libraries or other external closed source dependencies will be added in upcoming contributions from our side (at least we have no plan in doing so).
Finn
From: Stephen Hemminger [mailto:stephen@networkplumber.org]
Sent: 10. september 2016 20:31
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org; Finn Christensen <fc@napatech.com>; Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH v3] ntnic: add PMD driver
I think that if the driver is just a shim for proprietary code, then the vendor should just maintain it out of tree. 6wind and windriver already do this.
Disclaimer: This email and any files transmitted with it may contain confidential information intended for the addressee(s) only. The information is not to be surrendered or copied to unauthorized persons. If you have received this communication in error, please notify the sender immediately and delete this e-mail from your system.
next prev parent reply other threads:[~2016-09-12 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 13:44 [dpdk-dev] [PATCH] " Finn Christensen
2016-08-26 14:44 ` Thomas Monjalon
2016-08-26 16:32 ` Finn Christensen
2016-08-27 9:07 ` Thomas Monjalon
2016-08-26 16:54 ` Stephen Hemminger
2016-08-29 6:22 ` Finn Christensen
2016-08-29 10:04 ` Thomas Monjalon
2016-08-29 12:00 ` Finn Christensen
2016-09-08 11:14 ` [dpdk-dev] [PATCH v2] " Finn Christensen
2016-09-08 13:49 ` Neil Horman
2016-09-08 14:22 ` Finn Christensen
2016-09-09 12:48 ` [dpdk-dev] [PATCH v3] " Finn Christensen
2016-09-09 13:51 ` Neil Horman
2016-09-10 7:58 ` Finn Christensen
2016-09-10 8:20 ` Thomas Monjalon
2016-09-10 18:31 ` Stephen Hemminger
2016-09-12 8:08 ` Finn Christensen [this message]
2016-09-12 12:33 ` Neil Horman
2016-09-12 7:34 ` Finn Christensen
2016-11-21 13:47 ` Ferruh Yigit
2016-11-21 13:55 ` Finn Christensen
2016-09-12 12:32 ` Neil Horman
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=e2f0ee6c4d404108b9de30a4e8efafd2@napatech.com \
--to=fc@napatech.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=stephen@networkplumber.org \
--cc=thomas.monjalon@6wind.com \
/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).