DPDK usage discussions
 help / color / mirror / Atom feed
From: Sharon <sharon.t@altencalsoftlabs.com>
To: users@dpdk.org
Subject: [dpdk-users] Tx burst getting failed with Virtio driver
Date: Thu, 4 Apr 2019 12:55:10 +0530	[thread overview]
Message-ID: <9beaa13f-239a-5361-81ea-20d5237bf1be@altencalsoftlabs.com> (raw)
In-Reply-To: <9279c2f3-195c-0034-48e6-4246eee428a9@altencalsoftlabs.com>

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.

On enabling virtio pmd logs, following error is found:

PMD: virtio_xmit_pkts() tx: No free tx descriptors to transmit

*VM configuration:*

Cores: Total 12 cores, 5 cores for the application
OS: CentOS 7.2.1511
Linux kernel : 3.10.0-327.13.1.el7.x86_64
DPDK version : 17.05*
*

*Ring configuration in application:*

TX descriptor ring size: 4096
RX descriptor ring size: 1024
4 cores for rx and tx in a run to completion model.
Single port is used for Rx and Tx.
lcore to queue mapping is 1:1, i.e 1rx queue and 1tx queue per lcore

*ethtool -g eth0*
Ring parameters for eth0:
Pre-set maximums:
RX:             4096
RX Mini:           0
RX Jumbo:       0
TX:             4096
Current hardware settings:
RX:             4096
RX Mini:           0
RX Jumbo:       0
TX:             4096

*lscpu*

Architecture:            x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:              Little Endian
CPU(s):                     12
On-line CPU(s) list:    0-11
Thread(s) per core:  2
Core(s) per socket:   6
Socket(s):                 1
NUMA node(s):         1
Vendor ID:               GenuineIntel
CPU family:              6
Model:                     85
Model name:           Intel(R) Xeon(R) CPU @ 2.00GHz
Stepping:                 3
CPU MHz:                2000.168
BogoMIPS:              4000.33
Hypervisor vendor: KVM
Virtualization type:  full
L1d cache:              32K
L1i cache:               32K
L2 cache:                256K
L3 cache:                56320K
NUMA node0 CPU(s): 0-11

*NIC stats is provided below:*

100330695 packets input, 141154589263 bytes
100310198 packets output, 136450396190 bytes
0 packets missed
0 erroneous packets received
0 multicast packets received
0 failed transmitted packets
0 No Mbufs


Stats reg 0 RX-packets: 23454090 RX-errors: 0 RX-bytes: 32948589715
Stats reg 1 RX-packets: 23954850 RX-errors: 0 RX-bytes: 33699067521
Stats reg 2 RX-packets: 26014919 RX-errors: 0 RX-bytes: 36614183404
Stats reg 3 RX-packets: 26906836 RX-errors: 0 RX-bytes: 37892748623


Stats reg 0 TX-packets: 23450529 TX-bytes: 31934107195
Stats reg 1 TX-packets: 23951340 TX-bytes: 32591951998
Stats reg 2 TX-packets: 26008018 TX-bytes: 35366748482
Stats reg 3 TX-packets: 26900311 TX-bytes: 36557588515

Increasing the number of cores for the application is also not helping 
in this case.

Kindly suggest as what needs to be done to improve the performance and 
avoid this issue.

Thanks & Regards,
Sharon T N


       reply	other threads:[~2019-04-05 20:08 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 [this message]
2019-04-04  7:31   ` Sharon
2019-04-04 15:41     ` Stephen Hemminger
2019-04-05  6:42       ` Sharon

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=9beaa13f-239a-5361-81ea-20d5237bf1be@altencalsoftlabs.com \
    --to=sharon.t@altencalsoftlabs.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).