From: Vincent JARDIN <vincent.jardin@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Ed Warnicke <hagbard@gmail.com>,
Jaswinder Singh <jaswinder.singh@nxp.com>
Cc: Michael Dolan <mdolan@linuxfoundation.org>,
"Ed Warnicke (eaw)" <eaw@cisco.com>,
"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] DPDK + Linux Foundation - summary of fees
Date: Wed, 18 Jan 2017 00:46:15 +0100 [thread overview]
Message-ID: <433f3e10-ef3b-a6e9-636d-773e6a7f4846@6wind.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA722AA9DE@IRSMSX108.ger.corp.intel.com>
Le 17/01/2017 à 23:28, O'Driscoll, Tim a écrit :
> "I said that Red Hat is happy with the technical operation of the
> project, and we don't want to see the community disrupted with toolset
> changes - and it's possible to work with projects like fd.io, OVS, and
> OPNFV to do testing of DPDK.
>
> Representatives from Brocade, Cavium, and Linaro all voiced a preference
> for a stand-alone lightweight project"
+1 too
DPDK is consumed by many projects and it was proven to be a successful
model. By launching DPDK.org, 6WIND wanted to stimulate DPDK to be a
reference for many consumers of IOs (FD.io, ovs-dpdk, moongen, ostinato,
etc.) on any HW.
Since day 1 of DPDK.org, DPDK allows to sustain any innovations because
of a strong intent to be agnostic.
next prev parent reply other threads:[~2017-01-17 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 12:21 Vincent JARDIN
2017-01-11 15:12 ` Michael Dolan
2017-01-17 14:16 ` Jaswinder Singh
2017-01-17 20:10 ` Ed Warnicke
2017-01-17 22:28 ` O'Driscoll, Tim
2017-01-17 23:46 ` Vincent JARDIN [this message]
2017-01-18 17:11 ` George Zhao
2017-01-18 17:14 ` Michael Dolan
2017-01-18 17:19 ` George Zhao
2017-01-18 18:47 ` Vincent Jardin
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=433f3e10-ef3b-a6e9-636d-773e6a7f4846@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=eaw@cisco.com \
--cc=hagbard@gmail.com \
--cc=jaswinder.singh@nxp.com \
--cc=mdolan@linuxfoundation.org \
--cc=moving@dpdk.org \
--cc=tim.odriscoll@intel.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).