DPDK patches and discussions
 help / color / mirror / Atom feed
From: Asaf Penso <asafp@nvidia.com>
To: "bugzilla@dpdk.org" <bugzilla@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [Bug 924] Mellanox ConnectX6 DPDK dpdk-testpmd Receive error len error checksum UDP packet performance is very low!
Date: Wed, 26 Jan 2022 17:39:55 +0000	[thread overview]
Message-ID: <DM5PR1201MB25557E1FD15849CF8B763C96CD209@DM5PR1201MB2555.namprd12.prod.outlook.com> (raw)
In-Reply-To: <bug-924-3@http.bugs.dpdk.org/>

[-- Attachment #1: Type: text/plain, Size: 3521 bytes --]

You mention flow2 is with the errors, but also show the performance is good. is this correct?
Do you mean when you have errors you get perf drop?

Regards,
Asaf Penso
________________________________
From: bugzilla@dpdk.org <bugzilla@dpdk.org>
Sent: Thursday, January 20, 2022 11:01:43 AM
To: dev@dpdk.org <dev@dpdk.org>
Subject: [Bug 924] Mellanox ConnectX6 DPDK dpdk-testpmd Receive error len error checksum UDP packet performance is very low!

https://bugs.dpdk.org/show_bug.cgi?id=924

            Bug ID: 924
           Summary: Mellanox ConnectX6 DPDK dpdk-testpmd Receive error len
                    error checksum UDP packet performance is very low!
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: 188989801@qq.com
  Target Milestone: ---

I use Ixia to construct two streams
flow1 udp 64size small packet
flow2 udp 64size small packet error len error checksum
Send per second 30G bps  57 million pps


./dpdk-testpmd -l 4-22 -n 8 -- -i --rxq 19 --txq 19 --nb-cores 18 --rxd 2048
--txd 2048 --portmask 0xff

set fwd rxonly
start

  ######################## NIC statistics for port 6  ########################
  RX-packets: 178423861761 RX-missed: 646877     RX-bytes:  11419127182586
  RX-errors: 0
  RX-nombuf:  0
  TX-packets: 0          TX-errors: 0          TX-bytes:  0

  Throughput (since last show)
  Rx-pps:      5904277          Rx-bps:   3022990248
  Tx-pps:            0          Tx-bps:            0
  ############################################################################
Recive per second 3G bps 5 million pps ,Only about one tenth was received

rx_discards_phy drop
[root@localhost ~]#  ethtool -S enp202s0f0 |grep dis
     rx_discards_phy: 48832790759
     tx_discards_phy: 0
     rx_prio0_discards: 48832470594
     rx_prio1_discards: 0
     rx_prio2_discards: 0
     rx_prio3_discards: 0
     rx_prio4_discards: 0
     rx_prio5_discards: 0
     rx_prio6_discards: 0
     rx_prio7_discards: 0


When I change the flow2 to no problem udp, It's all normal.

  ######################## NIC statistics for port 6  ########################
  RX-packets: 179251451823 RX-missed: 660384     RX-bytes:  11472092947106
  RX-errors: 0
  RX-nombuf:  0
  TX-packets: 0          TX-errors: 0          TX-bytes:  0

  Throughput (since last show)
  Rx-pps:     57553942          Rx-bps:  29467618576
  Tx-pps:            0          Tx-bps:            0
  ############################################################################

Recive per second 29.4G bps 57 million pps



[root@localhost ~]# mlxfwmanager
Querying Mellanox devices firmware ...

Device #1:
----------

  Device Type:      ConnectX6
  Part Number:      MCX653106A-ECA_Ax
  Description:      ConnectX-6 VPI adapter card; H100Gb/s (HDR100; EDR IB and
100GbE); dual-port QSFP56; PCIe3.0 x16; tall bracket; ROHS R6
  PSID:             MT_0000000224
  PCI Device Name:  0000:ca:00.0
  Base MAC:         08c0eb204e5a
  Versions:         Current        Available
     FW             20.30.1004     20.32.1010
     PXE            3.6.0301       3.6.0502
     UEFI           14.23.0017     14.25.0017

  Status:           Update required

--
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 7136 bytes --]

      reply	other threads:[~2022-01-26 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  9:01 bugzilla
2022-01-26 17:39 ` Asaf Penso [this message]

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=DM5PR1201MB25557E1FD15849CF8B763C96CD209@DM5PR1201MB2555.namprd12.prod.outlook.com \
    --to=asafp@nvidia.com \
    --cc=bugzilla@dpdk.org \
    --cc=dev@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).