From: arun kumar <arunkumarsit@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] KNI implementation help needed
Date: Tue, 26 Jan 2016 01:08:25 -0800 [thread overview]
Message-ID: <CAGOgA2-AhSYcAyPcXR9oh=rXcGseSK5_M6k7-OnBjSETu28mFA@mail.gmail.com> (raw)
Hi All,
I need to integrate the KNI interface into my DPDK application which can
redirect the packets to Kernel stack.
But the DPDK “setup.py” script already creating one DPDK interface (dpdk0)
for the NIC port. Also the KNI interface creates one more logical interface
for the same NIC port. The creation of 2 logical interfaces for the same
NIC port creates issues in my application when I want to communicate to
external client.
So I want to use only one interface which can be used by DPDK application
and by KNI as well.
So, how to integrate KNI into DPDK applications?
-Arun
next reply other threads:[~2016-01-26 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 9:08 arun kumar [this message]
2016-01-26 10:28 ` Masoud Moshref Javadi
2016-01-27 20:28 ` arun kumar
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='CAGOgA2-AhSYcAyPcXR9oh=rXcGseSK5_M6k7-OnBjSETu28mFA@mail.gmail.com' \
--to=arunkumarsit@gmail.com \
--cc=users@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).