DPDK usage discussions
 help / color / mirror / Atom feed
From: "Yan, Xiaoping (NSB - CN/Hangzhou)" <xiaoping.yan@nokia-sbell.com>
To: Asaf Penso <asafp@nvidia.com>, "users@dpdk.org" <users@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	 Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-users] mlx5 VF packet lost between rx_port_unicast_packets and rx_good_packets
Date: Mon, 26 Jul 2021 04:52:19 +0000
Message-ID: <ea679ec0d4764fc1bf9acd0f2d3133fa@nokia-sbell.com> (raw)
In-Reply-To: <DM8PR12MB54944470428E409A757C08A4CD149@DM8PR12MB5494.namprd12.prod.outlook.com>


dpdk version in use is 19.11
I have not tried with latest upstream version.

It seems performance is affected by IPv6 neighbor advertisement packets coming to this interface
      05:20:04.025290 IP6 fe80::6cf1:9fff:fe4e:8a01 > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::6cf1:9fff:fe4e:8a01, length 32
              0x0000:  3333 0000 0001 6ef1 9f4e 8a01 86dd 6008
              0x0010:  fe44 0020 3aff fe80 0000 0000 0000 6cf1
              0x0020:  9fff fe4e 8a01 ff02 0000 0000 0000 0000
              0x0030:  0000 0000 0001 8800 96d9 2000 0000 fe80
              0x0040:  0000 0000 0000 6cf1 9fff fe4e 8a01 0201
              0x0050:  6ef1 9f4e 8a01
Somehow, there are about 100 such packets per second coming to the interface, and packet loss happens.
When we change default vlan in switch so that there is no such packets come to the interface (the mlx5 VF under test), there is not packet loss anymore.

In both cases, all packets have arrived to rx_vport_unicast_packets.
In the packet loss case, we see less packets in rx_good_packets (rx_vport_unicast_packets  = rx_good_packets + lost packet).
If the dpdk application is too slow to receive all packets from the VF, is there any counter to indicate this?

Any suggestion?
Thank you.

Best regards
Yan Xiaoping

-----Original Message-----
From: Asaf Penso <asafp@nvidia.com>
Sent: 2021年7月13日 20:36
To: Yan, Xiaoping (NSB - CN/Hangzhou) <xiaoping.yan@nokia-sbell.com>; users@dpdk.org
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: mlx5 VF packet lost between rx_port_unicast_packets and rx_good_packets

Hello Yan,

Can you please mention which DPDK version you use and whether you see this issue also with latest upstream version?

Asaf Penso

>-----Original Message-----
>From: users <users-bounces@dpdk.org<mailto:users-bounces@dpdk.org>> On Behalf Of Yan, Xiaoping (NSB -
>Sent: Monday, July 5, 2021 1:08 PM
>To: users@dpdk.org<mailto:users@dpdk.org>
>Subject: [dpdk-users] mlx5 VF packet lost between
>rx_port_unicast_packets and rx_good_packets
>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
>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
>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-26 11:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 10:07 Yan, Xiaoping (NSB - CN/Hangzhou)
2021-07-13 12:35 ` Asaf Penso
2021-07-26  4:52   ` Yan, Xiaoping (NSB - CN/Hangzhou) [this message]
     [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea679ec0d4764fc1bf9acd0f2d3133fa@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.com \
    --cc=asafp@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=users@dpdk.org \
    --cc=viacheslavo@nvidia.com \


* 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 http://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/ http://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

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