DPDK usage discussions
 help / color / mirror / Atom feed
From: Amarnath Nallapothula <Amarnath.Nallapothula@riverbed.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] occasionally traffic stalls due to rx and tx descriptor not available
Date: Thu, 5 Jul 2018 11:34:58 +0000	[thread overview]
Message-ID: <B381B160-DE44-480D-8AA2-E7BB3F561AD5@riverbed.com> (raw)

Hi Experts,

I am testing performance of my dpdk based application which forwards packets from port 1 to port 2 of 40G NIC card and via versa.Occasionally we see that packets rx and tx stops on one of the port. I looked through the dpdk’s fm10k driver’s code and found out that this could happen if rx/tx descriptors are not available.

To improve performance, I am using RSS functionality and created five rx and tx queue. Dedicated lcores are assigned to forward packets from port1 queue 0 to port2 queue 0 and via versa.

During port initialization rx_queue is initialized with 128 Rx ring descriptor size and tx_queue  is initialized 512 Tx ring descriptor. Threshold values are left default.

I have few queries here:

  1.  Is above initialization value for rx and tx descriptor is good for each queue for given port.
  2.  Under what conditions rx and tx descriptor gets exhausted?
  3.  Any suggestion or information you can provide to debug this issue?

Regards,
Amar

             reply	other threads:[~2018-07-05 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 11:34 Amarnath Nallapothula [this message]
2018-07-06  3:36 ` Hui Liu
2018-07-06 11:49   ` Amarnath Nallapothula
2018-07-26  2:31     ` Hui Liu
2018-07-26  4:41       ` Amarnath Nallapothula

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=B381B160-DE44-480D-8AA2-E7BB3F561AD5@riverbed.com \
    --to=amarnath.nallapothula@riverbed.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).