DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: DPDK Tx does not free mbufs
Date: Fri, 20 Sep 2024 19:34:00 +0000	[thread overview]
Message-ID: <CH3PR01MB84703261BF84F43348EB638D8F6C2@CH3PR01MB8470.prod.exchangelabs.com> (raw)

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

Hi,
I have Intel x710-DA4 NIC configured as SR-IOV or PCI-PT.

The DPDK 17.11 rte_eth_tx_burst() API says the packet is transmitted successfully, but over time the available mbufs continues to shrink until no mbufs available.
When I monitor the X710 port output I see the first mbuf transmitted from the X710 port but not the second mbuf.


I also made sure the tx.offloads has DEV_TX_OFFLOAD_MULTI_SEGS set if capability bit is set.
I reviewed the mbuf details (both first and second mbufs) and all looks correct and identical.
In DPDK 17.11 I see the failure but in DPDK 22.11 I don't see the failure.

Intel x710-DA4 driver/firmware is 1.11.1.31/6.80

Does anyone know why this occurs and how to fix it?  Is the issue in the Intel i40e driver?

Thanks,
Ed





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

                 reply	other threads:[~2024-09-20 19:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CH3PR01MB84703261BF84F43348EB638D8F6C2@CH3PR01MB8470.prod.exchangelabs.com \
    --to=ed.lombardo@netscout.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).