DPDK usage discussions
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: "Bing Zhao" <bingz@nvidia.com>,
	"Slava Ovsiienko" <viacheslavo@nvidia.com>,
	韩康康 <961373042@qq.com>, "Ori Kam" <orika@nvidia.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: net/mlx5: mellanox cx5 experiences "rx_phy_discard_packets" under low bandwidth conditions.
Date: Mon, 28 Apr 2025 07:01:16 +0000	[thread overview]
Message-ID: <CH3PR12MB846064573D4E42AFEFE70777A4812@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH7PR12MB69057F67A8521352451073A3D0812@PH7PR12MB6905.namprd12.prod.outlook.com>

Adding correct mail addresses for users mailing list and to Ori Kam.

> From: Bing Zhao <bingz@nvidia.com>
> Sent: Monday, April 28, 2025 9:00 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; 韩康康 <961373042@qq.com>; Dariusz Sosnowski <dsosnowski@nvidia.com>; orika <orika@nivida.com>
> Cc: users <users@dpdk.com>
> Subject: RE: net/mlx5: mellanox cx5 experiences "rx_phy_discard_packets" under low bandwidth conditions.
>
> Hi Kangkang,
>
> Please take the DPDK performance report and the configurations under DOC link of dpdk.org for a reference.
> It shows how to configure the HW and how to run the testpmd / l2fwd for SCP / ZPL testing. Or searching for the DPDK testing white paper from CTC as well(中国电信DPDK测试白皮书).
> In the docs, the NUMA / PCIe / lcore affinity / queue depths will all be explained inside.
>
> From: Slava Ovsiienko <mailto:viacheslavo@nvidia.com>
> Sent: Monday, April 28, 2025 1:57 PM
> To: 韩康康 <mailto:961373042@qq.com>; Dariusz Sosnowski <mailto:dsosnowski@nvidia.com>; Bing Zhao <mailto:bingz@nvidia.com>; orika <mailto:orika@nivida.com>
> Cc: users <mailto:users@dpdk.com>
> Subject: RE: net/mlx5: mellanox cx5 experiences "rx_phy_discard_packets" under low bandwidth conditions.
>
> Hi,
>
> First of all, please, increase the number of queues and handling cores. For 100GBps link from 4 to 8 queue/cores usually are needed.
> Also, you can try combinations of multiple queues per core (2..4 queues handled by one core).
> And there are the offload options “inline” and mprq might be useful to gain the wire speed  for the small packets.
> Please see the Nvidia/Mellanox performance reports (https://core.dpdk.org/perf-reports/) for the details.
>
> With best regards,
> Slava
>
> From: 韩康康 <mailto:961373042@qq.com>
> Sent: Friday, April 25, 2025 1:36 PM
> To: Dariusz Sosnowski <mailto:dsosnowski@nvidia.com>; Slava Ovsiienko <mailto:viacheslavo@nvidia.com>; Bing Zhao <mailto:bingz@nvidia.com>; orika <mailto:orika@nivida.com>
> Cc: users <mailto:users@dpdk.com>
> Subject: net/mlx5: mellanox cx5 experiences "rx_phy_discard_packets" under low bandwidth conditions.
>
>
> You don't often get email from mailto:961373042@qq.com. https://aka.ms/LearnAboutSenderIdentification
>
> Hi all,
> I am using dpdk-testpmd and pkt generator to test bandwith according to RFC2544.
> However, I observed that CX5 rx_phy_discard_packets at low bandwith, resulting in abnormal measurements under zero packet loss conditions.
>
> dpdk version: dpdk-21.11.5
> ethtool -i enp161s0f1np1:
>     driver: mlx5_core
>     version: 5.8-6.0.4
>     firmware-version: 16.32.1010
> Hardware: AMD EPYC 7742 64-core Processor
> dpdk-testpmd:
> dpdk-testpmd -l 96-111 -n 4 -a 0000:a1:00.1 -- -i --rxq=1  --txq=1 --txd=8192 --rxd=8192 --nb-cores=1  --burst=128 -a --mbcache=512  --rss-udp
> test result:
> frame size(bytes)    offerd Load(%)    packet loss rate
> 128                         15.69                   0.000211
> 256                         14.148                 0.0004
> 512                         14.148                 0.00008
> 1518                        14.92                  0.00099
>
> i'd like to ask, is this an issue with CX5 NIC? How can i debug it to eliminate the packet drops?
>
> 韩康康
> mailto:961373042@qq.com


       reply	other threads:[~2025-04-28  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_32F472A487C557D466BA2338E4FDF710A609@qq.com>
     [not found] ` <MN6PR12MB85678369DDCB1509C887F66ADF812@MN6PR12MB8567.namprd12.prod.outlook.com>
     [not found]   ` <PH7PR12MB69057F67A8521352451073A3D0812@PH7PR12MB6905.namprd12.prod.outlook.com>
2025-04-28  7:01     ` Dariusz Sosnowski [this message]
2025-04-28  7:02       ` Bing Zhao

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=CH3PR12MB846064573D4E42AFEFE70777A4812@CH3PR12MB8460.namprd12.prod.outlook.com \
    --to=dsosnowski@nvidia.com \
    --cc=961373042@qq.com \
    --cc=bingz@nvidia.com \
    --cc=orika@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).