DPDK patches and discussions
 help / color / mirror / Atom feed
From: zimeiw  <zimeiw@163.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev]  open data plane based on dpdk and netdp
Date: Fri, 7 Nov 2014 12:36:08 +0800 (CST)	[thread overview]
Message-ID: <2b962dba.7777.1498889bd74.Coremail.zimeiw@163.com> (raw)
In-Reply-To: <7e3aac11.12134.1490992a43f.Coremail.zimeiw@163.com>

hi,


NETDP news :
UDP protocol and part of socket layer are porting into NETDP.
Another application could establish UDP socket via NETDP, and could communicate with remote application on other PC.
Packets ZERO copy between application and NETDP.
No lock in UDP stack and socket layer.
Running on multiple cores.
Code link: https://github.com/opendp/dpdk-odp
Demo link:  https://github.com/opendp/dpdk-odp/wiki/Demo::UDP-socket
Next planning: testing performance and porting TCP to NETDP.


OPENDP (open data plane) news
Create an initial opendp (open data plane) process based on dpdk and netdp.
The purpose of OPENDP as below:
User could build up a data plane to handle level 3, level 4 traffic easily.
User could choice needed component to to setup data plane, of course currently the component is little.
All application with mass traffic could go though data plane.
OPENDP could also be fast path of software router.
and so on...
Code link: https://github.com/opendp/dpdk-odp/tree/master/opendp
--

Best Regards,
zimeiw

  reply	other threads:[~2014-11-07  4:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  7:18 [dpdk-dev] [PATCH] i40e: fix of compile error Helin Zhang
2014-10-13  7:28 ` Zhan, Zhaochen
2014-10-13 12:42 ` Zhan, Zhaochen
2014-10-13 12:54   ` [dpdk-dev] why no API to free a ring? zimeiw
2014-11-07  4:36     ` zimeiw [this message]
2014-10-15  7:51   ` [dpdk-dev] [PATCH] i40e: fix of compile error Thomas Monjalon

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=2b962dba.7777.1498889bd74.Coremail.zimeiw@163.com \
    --to=zimeiw@163.com \
    --cc=dev@dpdk.org \
    /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).