All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Clarylin L <clearasu@gmail.com>, dev@dpdk.org
Subject: Re: L3 Forwarding performance of DPDK on virtio
Date: Thu, 21 Jan 2016 09:25:10 +0800	[thread overview]
Message-ID: <56A03376.2030903@intel.com> (raw)
In-Reply-To: <CAKj5MjtyCmu_+smtGctWYJUjvUSFOuB3UAzM85rdKoRxig3k-Q@mail.gmail.com>


Hello!

On 1/21/2016 7:51 AM, Clarylin L wrote:
> I am running dpdk within a virtual guest as a L3 forwarder.
>
>
> The VM has two ports connecting to two linux bridges (in turn connecting
> two physical ports). DPDK is used to forward between these two ports (one
> port connected to traffic generator and the other connected to sink). I
> used iperf to test the throughput.
>
>
> If the VM/DPDK is running on passthrough, it can achieve around 10G
> end-to-end (from traffic generator to sink) throughput. However if the
> VM/DPDK is running on virtio (virtio-net-pmd), it achieves just 150M
> throughput, which is a huge degrade.
>
>
> On the virtio, I also measured the throughput between the traffic generator
> and its connected port on VM, as well as throughput between the sink and
> it's VM port. Both legs show around 7.5G throughput. So I guess forwarding
> within the VM (from one port to the other) would be a big killer of the
> performance.
>
>
> Any suggestion on how I can root cause the poor performance issue, or any
> idea on performance tuning techniques for virtio? thanks a lot!

The L3 forwarder, you mentioned, is the l3fwd example in DPDK? If so, I 
doubt it can work well with virtio, see another thread "Add API to get 
packet type info".

Thanks,
Jianfeng

  reply	other threads:[~2016-01-21  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 23:51 L3 Forwarding performance of DPDK on virtio Clarylin L
2016-01-21  1:25 ` Tan, Jianfeng [this message]
2016-01-21  3:18   ` Clarylin L

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=56A03376.2030903@intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=clearasu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.