DPDK usage discussions
 help / color / mirror / Atom feed
From: Sharon <sharon.t@altencalsoftlabs.com>
To: Stephen Hemminger <stephen@networkplumber.org>, users@dpdk.org
Subject: Re: [dpdk-users] Tx burst getting failed with Virtio driver
Date: Fri, 5 Apr 2019 12:12:00 +0530	[thread overview]
Message-ID: <cd774a6c-486d-f3cc-3759-12e3b3a5587b@altencalsoftlabs.com> (raw)
In-Reply-To: <20190404084110.76def58a@shemminger-XPS-13-9360>

Hi,

Regarding pps,

6 Gbps comes around to be less than 0.6 Mpps with packet size 1300 Bytes.

Also, in a GCP VM instance, virtio is able to process 10 Gbps easily 
with 5-6 cores. (without DPDK)

Kindly advice.

Thanks & Regards,
Sharon T N


On 04/04/19 9:11 PM, Stephen Hemminger wrote:
> On Thu, 4 Apr 2019 13:01:16 +0530
> Sharon <sharon.t@altencalsoftlabs.com> wrote:
>
>> Hi,
>>
>> With a dpdk based application inside GCP VM instance,
>> it is observed that while sending UDP packets of length 1300 at around 6
>> Gbps rate, tx burst starts failing frequently.
> Virtio (like all devices) can only transmit so fast.
> If you transmit faster than the host can consume, the queue will get full
> this shows up in DPDK when all transmit descriptors are used.
>
> 6Gbps is about 4.4 Mpps and the upper bound on virtio is usually about 1 to 2 Mpps
> because of the overhead of host processing (vhost and linux bridge).
>

      reply	other threads:[~2019-04-05  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9279c2f3-195c-0034-48e6-4246eee428a9@altencalsoftlabs.com>
2019-04-04  7:25 ` Sharon
2019-04-04  7:31   ` Sharon
2019-04-04 15:41     ` Stephen Hemminger
2019-04-05  6:42       ` Sharon [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=cd774a6c-486d-f3cc-3759-12e3b3a5587b@altencalsoftlabs.com \
    --to=sharon.t@altencalsoftlabs.com \
    --cc=stephen@networkplumber.org \
    --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).