DPDK usage discussions
 help / color / mirror / Atom feed
From: Sangjin Han <Sangjin.Han@spacex.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "matan@nvidia.com" <matan@nvidia.com>,
	"viacheslavo@nvidia.com" <viacheslavo@nvidia.com>
Subject: mlx5: Packet drops without RX queue overflow?
Date: Tue, 23 Aug 2022 20:54:08 +0000	[thread overview]
Message-ID: <9A6B914B-DC01-4AAA-B582-DF6D63408651@spacex.com> (raw)

Hi All,

I am seeing RX packet drops on a ConnectX-5 100G NIC. Even at a low input rate, e.g., 2Mpps and 20Gbps, about 0.1% of packets are being dropped. The setup is as follows:

* DPDK 21.08
* one mlx5 VF with SR-IOV (VLAN)
* a DPDK application running on 16 cores.
* 16 RX queues, with 2,048 descriptors for each
* tried both scalar / vector versions of RX burst functions.

I observe that packets are being lost, from reading the rx_discards_phy counter with ethtool for the PF. No relevant counter is found for the VF.

I checked the usual suspect -- CPU not being fast enough to drain the RX queues, causing overflow -- but it doesn't seem to be the case. I checked the queue occupancy with rte_eth_rx_queue_count() before every rte_eth_rx_burst(), but it mostly stays below 10% and never exceeded 20% while packets being dropped. Given that it loses packets without RX queue overflow, its behavior resembles flow control based on watermarks or Random Early Drop.

Does anyone have any suggestions that I can try? I tried various tuning parameters via ethtool, latest NIC firmware, etc., and the problem still exists.

Thanks,
Sangjin


                 reply	other threads:[~2022-08-23 20:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9A6B914B-DC01-4AAA-B582-DF6D63408651@spacex.com \
    --to=sangjin.han@spacex.com \
    --cc=matan@nvidia.com \
    --cc=users@dpdk.org \
    --cc=viacheslavo@nvidia.com \
    /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).