All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1958] Broadcom bnxt RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE always on
Date: Wed, 17 Jun 2026 14:51:42 +0000	[thread overview]
Message-ID: <bug-1958-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1958

            Bug ID: 1958
           Summary: Broadcom bnxt RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE always
                    on
           Product: DPDK
           Version: 26.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: riaan.wiid@vastech.co.za
  Target Milestone: ---

Environment
===========

dpdk-26.03 (tag v26.03)
OS: Rocky Linux (9.3 (Blue Onyx))
HW: Broadcom BCM57414 NetXtreme-E 10Gb/25Gb
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Description of Problem
======================

RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE is always enabled if not enabling PTP support
on a NIC port. In our case we are not enabling PTP support which means
RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE is enabled by default on all queues, which is
undesired behaviour when making use of Mbuf refcnt in our designs.

This behaviour seems to have started after this commit
https://github.com/DPDK/dpdk/commit/5722ed1aafd2fc5ad44e432a4f6c7bd337c673d8

RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE cannot be disabled through the offloads
specified in either rte_eth_dev_configure() or rte_eth_tx_queue_setup()

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

                 reply	other threads:[~2026-06-17 14:51 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=bug-1958-3@http.bugs.dpdk.org/ \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.