From: Gal Sagie <gal.sagie@gmail.com>
To: Deepak Sehrawat <d.sehrawat@gmail.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Fast Path Query
Date: Wed, 14 Jan 2015 08:24:52 +0200 [thread overview]
Message-ID: <CAG9LJa6BYoVcQnAy+wJ5bAgNjAE-W_xjcP512C_th3+fg99Qsw@mail.gmail.com> (raw)
In-Reply-To: <CAH+GhRnNPBujBRXcodpNqioJ4NmdXK=6_a876z+6v5Z+CWC74Q@mail.gmail.com>
Your application (which you build on top of DPDK) needs to filter which
traffic is control traffic and inject
it into the network stack.
You can leverage DPDK KNI for that (
http://dpdk.org/doc/guides/prog_guide/kernel_nic_interface.html)
Keep in mind you also need to take care of the TX side.
On Wed, Jan 14, 2015 at 8:16 AM, Deepak Sehrawat <d.sehrawat@gmail.com>
wrote:
> Hi All,
>
> I have a use-case where my slow path application (control path) is to run
> on Linux where as my data path is to run as DPDK application. Because both
> control and data packets are going to be received via same NIC card, how
> will these two flows be separated and passed on to Linux control app and
> DPDK data path app respectively? In short I want to understand how NIC
> received packets are separated between Linux Eth driver and PMD (poll mode
> driver) of DPDK?
>
> Thanks for the help in advance.
>
> Thanks,
> Deepak
>
--
Best Regards ,
The G.
next prev parent reply other threads:[~2015-01-14 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 6:16 Deepak Sehrawat
2015-01-14 6:24 ` Gal Sagie [this message]
2015-01-14 7:47 ` Zhang, Helin
2015-01-14 7:58 ` Deepak Sehrawat
2015-01-14 8:02 ` Zhang, Helin
[not found] ` <CAH+GhRmonvEv=JsRY8T4ykYDkfFfvHat=HX_nDyRg=sz1dQ6rg@mail.gmail.com>
[not found] ` <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E8648@SHSMSX104.ccr.corp.intel.com>
[not found] ` <CAH+GhRm-yvJw6iZvoxXChKPYyuWJDsFZLtPTk4DENHPYc+bAXg@mail.gmail.com>
2015-01-15 6:46 ` Zhang, Helin
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=CAG9LJa6BYoVcQnAy+wJ5bAgNjAE-W_xjcP512C_th3+fg99Qsw@mail.gmail.com \
--to=gal.sagie@gmail.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).