DPDK usage discussions
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Charles Oluwaseun Oluboyo <charlesboyo@gmail.com>
Cc: <users@dpdk.org>
Subject: Re: Unable to initialize ConnectX-4 ports in DPDK 24.11 and 25.03
Date: Tue, 27 May 2025 10:29:51 +0200	[thread overview]
Message-ID: <20250527082918.uurt6ewbhveldici@ds-vm-debian.local> (raw)
In-Reply-To: <CAPD_G3JeYeKmcfX0Yr8G7gScWvrLFwxMp4B2Pz6zqUc0aDxHnw@mail.gmail.com>

Hi,

On Sat, May 24, 2025 at 01:50:45AM +0100, Charles Oluwaseun Oluboyo wrote:
> Hello,
> 
> I have a ConnectX-4 dual-100Gbps NIC that works with DPDK versions
> 24.03 and 24.07 but not with 24.11 or 25.03.
> 
> 0000:04:00.0 'MT27700 Family [ConnectX-4] 1013' numa_node=0
> if=enp4s0f0np0 drv=mlx5_core unused=vfio-pci
> 0000:04:00.1 'MT27700 Family [ConnectX-4] 1013' numa_node=0
> if=enp4s0f1np1 drv=mlx5_core unused=vfio-pci
> 
> Setting the log levels to debug, the newer versions are unable to
> configure more than one (1) description on any queue:
> 
> ETHDEV: Invalid value for nb_tx_desc(=1024), should be: <= 1, >= 0,
> and a product of 1
> 
> Whereas using the older version, I am able to set a larger number of
> descriptors. Tried 512, 1024, 2048 and 4096.
> 
> ********************* Infos for port 0  *********************
> MAC address: EC:0D:9A:35:1A:16
> Device name: 04:00.0
> Driver name: mlx5_pci
> Firmware-version: 12.24.1000
> Devargs:
> Connect to socket: 0
> memory allocation on the socket: 0
> Link status: up
> Link speed: 100 Gbps
> Link duplex: full-duplex
> Autoneg status: On
> MTU: 2030
> Promiscuous mode: enabled
> Allmulticast mode: disabled
> Maximum number of MAC addresses: 128
> Maximum number of MAC addresses of hash filtering: 0
> VLAN offload:
>   strip off, filter off, extend off, qinq strip off
> Hash key size in bytes: 40
> Redirection table size: 4
> Supported RSS offload flow types:
>   ipv4  ipv4-frag  ipv4-tcp  ipv4-udp  ipv4-other  ipv6
>   ipv6-frag  ipv6-tcp  ipv6-udp  ipv6-other  ipv6-ex
>   ipv6-tcp-ex  ipv6-udp-ex  esp  l4-dst-only  l4-src-only
>   l3-dst-only  l3-src-only
> Minimum size of RX buffer: 32
> Maximum configurable length of RX packet: 65536
> Maximum configurable size of LRO aggregated packet: 65280
> Current number of RX queues: 4
> Max possible RX queues: 1024
> Max possible number of RXDs per queue: 65535
> Min possible number of RXDs per queue: 0
> RXDs number alignment: 1
> Current number of TX queues: 4
> Max possible TX queues: 1024
> Max possible number of TXDs per queue: 65535
> Min possible number of TXDs per queue: 0
> TXDs number alignment: 1
> Max segment number per packet: 40
> Max segment number per MTU/TSO: 40
> Device capabilities: 0x10( FLOW_SHARED_OBJECT_KEEP )
> Switch name: 04:00.0
> Switch domain Id: 0
> Switch Port Id: 65535
> Device error handling mode: none
> Device private info:
>   none
> 
> Is this a known issue? Please, what should I do next?
> 
> Oluwaseun

One of the patches merged to 24.11 introduced an issue with queues
descriptor limits on older NICs.

A patch with a fix for that is pending for merge to 25.07.

Would you be able apply the following patches and test on your side?

- https://patches.dpdk.org/project/dpdk/patch/20250424133128.133900-1-viacheslavo@nvidia.com/
- https://patches.dpdk.org/project/dpdk/patch/20250514075530.419423-1-viacheslavo@nvidia.com/

Best regards,
Dariusz Sosnowski

  reply	other threads:[~2025-05-27  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-24  0:50 Charles Oluwaseun Oluboyo
2025-05-27  8:29 ` Dariusz Sosnowski [this message]
2025-05-27 18:12   ` Charles Oluwaseun Oluboyo
2025-05-28 23:00     ` Charles Oluwaseun Oluboyo

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=20250527082918.uurt6ewbhveldici@ds-vm-debian.local \
    --to=dsosnowski@nvidia.com \
    --cc=charlesboyo@gmail.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).