From: "Polehn, Mike A" <mike.a.polehn@intel.com>
To: Kury Nicolas <nicolas.kury@master.hes-so.ch>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Does anybody know OpenDataPlane
Date: Wed, 2 Dec 2015 16:32:26 +0000 [thread overview]
Message-ID: <745DB4B8861F8E4B9849C970520ABBF1498366E7@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <DB3PR01MB0761965A561FA38FF8A8307BEC0E0@DB3PR01MB0761.eurprd01.prod.exchangelabs.com>
I don't think you have researched this enough.
Asking this questions shows that you are just beginning your research or do not understand how this fits into current telco NFV/SDN efforts.
Why does this exist: "OpenDataPlane using DPDK for Intel NIC", listed below? Why would competing technologies use the competition technology to solve a problem?
Maybe you can change your thesis to "Current Open Source Dataplane Methods": and do a comparison between the two. However if you just look at the sales documentation then you may not understand the real difference.
Mike
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kury Nicolas
Sent: Wednesday, December 2, 2015 6:22 AM
To: dev@dpdk.org
Subject: [dpdk-dev] Does anybody know OpenDataPlane
Hi!
Does anybody know OpenDataPlane ? http://www.opendataplane.org/ It is a framework designed to enable software portability between networking SoCs, regardless of the underlying instruction set architecture. There are several implementations.
* OpenDataPlane using DPDK for Intel NIC
* OpenDataPlane using DPAA for Freescale platforms (QorIQ)
* OpenDataPlane using MCSDK for Texas Insturments platforms (KeyStone II)
* etc.
When a developer wants to port his application, he just needs to recompile it with the implementation of OpenDataPlane related to the new platform.
I'm doing my Master's Thesis on OpenDataPlane and I have some questions.
- Now that OpenDataPlane (ODP) exists, schould every developpers start a new project with ODP or are there some reasons to still use DPDK ? What do you think ?
Thank you very much
Nicolas
next prev parent reply other threads:[~2015-12-02 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:21 Kury Nicolas
2015-12-02 16:32 ` Polehn, Mike A [this message]
2015-12-02 16:49 ` Polehn, Mike A
[not found] ` <00B2C372B6E6DA4FB04934511BF0564A3EFA7FF0@FMSMSX114.amr.corp.intel.com>
2015-12-03 8:15 ` Kury Nicolas
2015-12-03 9:46 Kury Nicolas
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=745DB4B8861F8E4B9849C970520ABBF1498366E7@ORSMSX102.amr.corp.intel.com \
--to=mike.a.polehn@intel.com \
--cc=dev@dpdk.org \
--cc=nicolas.kury@master.hes-so.ch \
/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).