DPDK usage discussions
 help / color / mirror / Atom feed
From: Gerry Wan <gerryw@stanford.edu>
To: users@dpdk.org
Subject: Re: [dpdk-users] mlx5: packets lost between good+discard and phy counters
Date: Sat, 10 Apr 2021 18:31:10 -0700
Message-ID: <CAAcwi3_7d7jGq5=LMQdrOf6aQdXG8MyDHuUgyqOgjm-x3yenVQ@mail.gmail.com> (raw)
In-Reply-To: <CAAcwi3_WGY9SGmL9kbJ3X_XojfjqFO7yZ4y8hKQN55Zfad3n0g@mail.gmail.com>

After further investigation, I think this may be a bug introduced in DPDK
v20.11, where these "lost" packets should be counted as "rx_out_of_buffer"
and "rx_missed_errors". On v20.08 both of these counters increment, but on
v20.11 and v21.02 these counters always remain 0.

Any workarounds for this? This is an important statistic for my use case.

On Fri, Apr 2, 2021 at 5:03 PM Gerry Wan <gerryw@stanford.edu> wrote:

> I have a simple forwarding experiment using a mlx5 NIC directly connected
> to a generator. I am noticing that at high enough throughput,
> rx_good_packets + rx_phy_discard_packets may not equal rx_phy_packets.
> Where are these packets being dropped?
>
> Below is an example xstats where I receive at almost the limit of what my
> application can handle with no loss. It shows rx_phy_discard_packets is 0
> but the number actually received by the CPU is less than rx_phy_packets.
> rx_out_of_buffer and other errors are also 0.
>
> I have disabled Ethernet flow control via rte_eth_dev_flow_ctrl_set with
> mode = RTE_FC_NONE, if that matters.
>
> {
>     "rx_good_packets": 319992439,
>     "tx_good_packets": 0,
>     "rx_good_bytes": 19199546340,
>     "tx_good_bytes": 0,
>     "rx_missed_errors": 0,
>     "rx_errors": 0,
>     "tx_errors": 0,
>     "rx_mbuf_allocation_errors": 0,
>     "rx_q0_packets": 319992439,
>     "rx_q0_bytes": 19199546340,
>     "rx_q0_errors": 0,
>     "rx_wqe_errors": 0,
>     "rx_unicast_packets": 319999892,
>     "rx_unicast_bytes": 19199993520,
>     "tx_unicast_packets": 0,
>     "tx_unicast_bytes": 0,
>     "rx_multicast_packets": 0,
>     "rx_multicast_bytes": 0,
>     "tx_multicast_packets": 0,
>     "tx_multicast_bytes": 0,
>     "rx_broadcast_packets": 0,
>     "rx_broadcast_bytes": 0,
>     "tx_broadcast_packets": 0,
>     "tx_broadcast_bytes": 0,
>     "tx_phy_packets": 0,
>     "rx_phy_packets": 319999892,
>     "rx_phy_crc_errors": 0,
>     "tx_phy_bytes": 0,
>     "rx_phy_bytes": 20479993088,
>     "rx_phy_in_range_len_errors": 0,
>     "rx_phy_symbol_errors": 0,
>     "rx_phy_discard_packets": 0,
>     "tx_phy_discard_packets": 0,
>     "tx_phy_errors": 0,
>     "rx_out_of_buffer": 0,
>     "tx_pp_missed_interrupt_errors": 0,
>     "tx_pp_rearm_queue_errors": 0,
>     "tx_pp_clock_queue_errors": 0,
>     "tx_pp_timestamp_past_errors": 0,
>     "tx_pp_timestamp_future_errors": 0,
>     "tx_pp_jitter": 0,
>     "tx_pp_wander": 0,
>     "tx_pp_sync_lost": 0,
> }
>
>

  reply	other threads:[~2021-04-11  1:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  0:03 Gerry Wan
2021-04-11  1:31 ` Gerry Wan [this message]
2021-04-13 13:39   ` Tom Barbette
2021-04-14 11:15     ` Asaf Penso
2021-04-14 19:13       ` Gerry Wan

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='CAAcwi3_7d7jGq5=LMQdrOf6aQdXG8MyDHuUgyqOgjm-x3yenVQ@mail.gmail.com' \
    --to=gerryw@stanford.edu \
    --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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git