From: Avi Cohen <avi.cohen@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] running pkt-gen in a container
Date: Wed, 28 Dec 2016 12:57:35 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361A01A64@lhreml501-mbb> (raw)
Hello
I have the following setup:
Ovs-dpdk is running in a VM.
I have 1 dpdk type port in the OVS (connected to the NIC w SR-IOV).
I have an LXC-container (or for simplicity a network namespace) in the VM - currently connected to the OVS via veth-pair.
I want to run pkt-get in the namespace - my questions:
1. I guess I have to run another DPDK instance in the namespace - to run pkt-gen on top of DPD, correct ? (i.e. - cannot use the ovs-dpdk instance ) 2. How to connect the namespace to the OVS in order to achieve zero copy ? (I guess veth is not suitable for that) - can I use vHost-user netdev or ivshmem, to connet ovs with the namespace ?
3. In cont. to question 2 - what interface should I bind to the DPDK instance running in the namespace Thanks in advance Avi
reply other threads:[~2016-12-28 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=B84047ECBD981D4B93EAE5A6245AA361A01A64@lhreml501-mbb \
--to=avi.cohen@huawei.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).