From: "Zhou, Danny" <danny.zhou@intel.com>
To: Deepak Sehrawat <d.sehrawat@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Sharing NIC port between Linux and DPDK
Date: Mon, 19 Jan 2015 06:37:59 +0000 [thread overview]
Message-ID: <DFDF335405C17848924A094BC35766CF0AA40E05@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAH+GhRmCPqPFUXgBb-rfghjNNGB_PbohyEERN_GmX=yZztMWxg@mail.gmail.com>
DPDK KNI(Kernel NIC interface) is your only option before bifurcated driver is adopted.
Basically, DPDK rx/tx all packets and do flow classification (e.g. 5-tuple based) in user
space then distribute control plane packets to KNI netdev in kernel space via
lockless queue based ring. The KNI netdev registers to kernel TCP/IP stack and
push control plane packets all the way up to the Linux user space control plane
applications.
If you have user space TCP/IP stacks and requires very high control plane performance,
you might take a short path by distributing control plane packets to your applications
directly. The reason we have KNI is that it could leverage mature enough TCP/IP stacks,
at the cost of CPU cycles.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Deepak Sehrawat
> Sent: Monday, January 19, 2015 2:23 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Sharing NIC port between Linux and DPDK
>
> Hi All,
>
> What are the various means available (as of now) to share a NIC port
> between Linux and DPDK applications? Idea is to separate control packets
> and data packets; using Linux userspace application to process control
> packets while DPDK application to access/process data packets (same NIC
> port is carrying both of these packet traffics; control as well as data).
>
> Note: Bifurcated driver is next step but it's not available as of now.
>
>
> Thanks,
> Deepak
prev parent reply other threads:[~2015-01-19 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 6:22 Deepak Sehrawat
2015-01-19 6:37 ` Zhou, Danny [this message]
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=DFDF335405C17848924A094BC35766CF0AA40E05@SHSMSX104.ccr.corp.intel.com \
--to=danny.zhou@intel.com \
--cc=d.sehrawat@gmail.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).