From: Ivano Cerrato <8002onavi@gmail.com>
To: "Zhu, Heqing" <heqing.zhu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] veth interfaces
Date: Tue, 03 Jun 2014 14:51:24 +0200 [thread overview]
Message-ID: <538DC4CC.3050902@gmail.com> (raw)
In-Reply-To: <CAD16F236028A64DBBC0158B1636EA4510EB0973@SHSMSX104.ccr.corp.intel.com>
Hello,
thanks for the answer.
Using the KNI API, I create a new interface, and then I "push it into
the container".
At this point, from the container, I send traffic and it is received in
the KNI example program.
Instead, in my understanding, it is not possible to attach KNI to an
already existing interface. Am I right?
Thank you,
Ivano
Il 30/05/2014 14:49, Zhu, Heqing ha scritto:
> Hi Ivano,
>
> I think you can use the KNI, there is example/kni and doc. Please visit if you have not done it. Please keep us updated on your journey with Docker containers. :-)
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ivano Cerrato
> Sent: Friday, May 30, 2014 3:02 PM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] veth interfaces
>
> Hello,
> I apologize for the imprecise email I sent, and now I try to be more specific about what I would like to do.
>
> I have a module that receives traffic from the network using DPDK and, based on the packet content, should provide packets to the proper Docker container.
> Docker containers receive packets through a veth interface.
>
> Can I use DPDK features, in particular the KNI, to send packets on a veth interface?
> If the KNI is not appropriate, is there something else that I could use?
>
> Regards,
>
> Ivano
prev parent reply other threads:[~2014-06-03 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 11:50 Ivano Cerrato
2014-05-30 7:02 ` Ivano Cerrato
2014-05-30 12:49 ` Zhu, Heqing
2014-06-03 12:51 ` Ivano Cerrato [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=538DC4CC.3050902@gmail.com \
--to=8002onavi@gmail.com \
--cc=dev@dpdk.org \
--cc=heqing.zhu@intel.com \
/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).