DPDK usage discussions
 help / color / mirror / Atom feed
From: "Yan, Xiaoping (NSB - CN/Hangzhou)" <xiaoping.yan@nokia-sbell.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] mlx5 VF packet lost between rx_port_unicast_packets and rx_good_packets
Date: Mon, 5 Jul 2021 10:07:38 +0000	[thread overview]
Message-ID: <0fbb0c1b5a2b4fd3b95d7238db101698@nokia-sbell.com> (raw)

Hi,

When doing traffic loopback test on a mlx5 VF, we found there are some packet loss (not all packet received back ).

From xstats counters, I found all packets have been received in rx_port_unicast_packets, but rx_good_packets has lower counter, and rx_port_unicast_packets - rx_good_packets = lost packets
i.e. packet lost between rx_port_unicast_packets and rx_good_packets.
But I can not find any other counter indicating where exactly those packets are lost.

Any idea?

Attached is the counter logs. (bf is before the test, af is after the test, fp-cli dpdk-port-stats is the command used to get xstats, and ethtool -S _f1 (the vf used) also printed)
Test equipment reports that it sends: 2911176 packets, receives:  2909474, dropped: 1702
And the xstats (after - before) shows rx_port_unicast_packets 2911177,  rx_good_packets 2909475, so drop (2911177 - rx_good_packets) is 1702

BTW, I also noticed this discussion "packet loss between phy and good counter"
http://mails.dpdk.org/archives/users/2018-July/003271.html
but my case seems to be different as packet also received in  rx_port_unicast_packets, and I checked counter from pf  (ethtool -S ens1f0 in attached log), rx_discards_phy is not increasing.

Thank you.

Best regards
Yan Xiaoping


             reply	other threads:[~2021-07-12 16:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 10:07 Yan, Xiaoping (NSB - CN/Hangzhou) [this message]
2021-07-13 12:35 ` Asaf Penso
2021-07-26  4:52   ` Yan, Xiaoping (NSB - CN/Hangzhou)
     [not found]     ` <DM8PR12MB54940E42337767B960E6BD28CDA69@DM8PR12MB5494.namprd12.prod.outlook.com>
     [not found]       ` <16515cb8ebbb4e7d833914040fa5943f@nokia-sbell.com>
     [not found]         ` <df15fbaac9a644fa93c55e1cfbc9226b@nokia-sbell.com>
     [not found]           ` <DM8PR12MB5494A1A84DA28E47CCB7496ECDA99@DM8PR12MB5494.namprd12.prod.outlook.com>
     [not found]             ` <22e029bf2ae6407e910cb2dcf11d49ce@nokia-sbell.com>
     [not found]               ` <e8e7cf781dd444fa9648facfc824d4c9@nokia-sbell.com>
     [not found]                 ` <4b0dd266b53541c7bc4964c29e24a0e6@nokia-sbell.com>
2021-09-30  8:05                   ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14  6:55                     ` Asaf Penso
2021-10-14  9:33                       ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14  9:50                         ` Asaf Penso
2021-10-14 10:15                           ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14 11:48                             ` Asaf Penso
2021-10-18  9:28                               ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-18 10:45                                 ` David Marchand
2021-10-27  6:17                                   ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-27  7:26                                     ` David Marchand
2021-10-27  7:54                                     ` Martin Weiser
2021-10-28  1:39                                       ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-28  1:58                                         ` Gerry Wan
2021-10-29  0:44                                           ` Yan, Xiaoping (NSB - CN/Hangzhou)

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=0fbb0c1b5a2b4fd3b95d7238db101698@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.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).