From: Yossi Barshishat <beyossi@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] vm2vm and host2vm performance using dpdk 16.11
Date: Tue, 15 Nov 2016 21:57:21 +0000 [thread overview]
Message-ID: <CAPOT950x-wecqReNeiqsjkCmFuKShaRSUJbz2ZfOmaxX6-rwWQ@mail.gmail.com> (raw)
Hi,
My simple setup includes 3VMs, each is running a forwarding dpdk based
program (e.g. l3fwd), all are located on one single host.
The setup looks like:
82599NIC1 ---> VM1 ---> VM2 ---VM3 ---> 82599NIC2
vm2vm nics use virtion and NIC-vm is PCI passthrough.
while generating 10g into first NIC resulted end to end performance are
extremely poor.
after removing VM2 performance are still poor.
I am using DPDK 16.11 over ubuntu 16.04 and looking for means to accelerate
performance.
- vhost-net can only have one single port and I fail to run a secondary
vhost-switch on the host, so it is not a good solution.
- ivshmem was removed from 16.11
- memnic - looks like incompatible with 16.11
Any idea what could be good mean for achieving good performance on the
following: host-2-vm / vm-2-host, vm-2-vm ?
Thanks
Yossi
next reply other threads:[~2016-11-15 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 21:57 Yossi Barshishat [this message]
2016-11-16 7:49 ` Yossi Barshishat
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=CAPOT950x-wecqReNeiqsjkCmFuKShaRSUJbz2ZfOmaxX6-rwWQ@mail.gmail.com \
--to=beyossi@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).