DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Wolfe <rnwolfe@google.com>
To: dev@dpdk.org, Junfeng Guo <junfeng.guo@intel.com>,
	 Joshua Washington <joshwash@google.com>
Cc: stable@dpdk.org, Harshitha Ramamurthy <hramamurthy@google.com>,
	 Rushil Gupta <rushilg@google.com>
Subject: [PATCH v2 0/3] net/gve: fix GQI Tx cleanup and QPL FIFO reclaim
Date: Tue, 17 Nov 2026 09:11:41 -0500	[thread overview]
Message-ID: <cover.1794908231.git.rnwolfe@google.com> (raw)
In-Reply-To: <20261115140016.3830109-1-rnwolfe@google.com>

This series fixes three independent bugs in the GQI Tx paths of net/gve:

- 1/3 clears the first freed sw_ring entry in gve_free_bulk_mbuf() so
  completed or refcounted segments do not leave stale mbuf pointers that
  are freed a second time on queue stop or release.
- 2/3 fixes GQI_RDA multi-segment non-TSO packet descriptors to pass
  data_len instead of pkt_len for the head segment, reclaims completed
  descriptors when nb_free runs low mid-burst, and stops counting normal
  ring-full backpressure as stats.errors.
- 3/3 fixes GQI_QPL jumbo Tx FIFO reclaim, TSO pre-allocation space
  checks, malformed TSO mbuf handling, and doorbell flushing.

v2:
- split v1 into three atomic Fixes patches for stable backporting
- free and count malformed TSO mbufs (pkt_len <= hlen) in
  gve_tx_burst_qpl() while tracking nb_sent separately from nb_tx so an
  invalid TSO request cannot stall the queue at tx_pkts[0]
- use for (;;) and add the missing blank line after
  gve_tx_reclaim_fifo_qpl()

Ryan Wolfe (3):
  net/gve: clear first freed slot in bulk mbuf free
  net/gve: fix GQI RDA multi-seg descriptor length and clean
  net/gve: fix GQI QPL jumbo Tx FIFO reclaim and doorbell

 drivers/net/gve/gve_tx.c | 78 ++++++++++++++++++++++++++++------------
 1 file changed, 55 insertions(+), 23 deletions(-)


  reply	other threads:[~2026-11-18  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 14:00 [PATCH] net/gve: fix GQI QPL jumbo Tx FIFO reclaim and doorbell Ryan Wolfe
2026-11-17 14:11 ` Ryan Wolfe [this message]
2026-11-17 14:11   ` [PATCH v2 1/3] net/gve: clear first freed slot in bulk mbuf free Ryan Wolfe
2026-11-17 14:11   ` [PATCH v2 2/3] net/gve: fix GQI RDA multi-seg descriptor length and clean Ryan Wolfe
2026-11-17 14:11   ` [PATCH v2 3/3] net/gve: fix GQI QPL jumbo Tx FIFO reclaim and doorbell Ryan Wolfe
2026-11-17 17:34 ` [PATCH] " Stephen Hemminger

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=cover.1794908231.git.rnwolfe@google.com \
    --to=rnwolfe@google.com \
    --cc=dev@dpdk.org \
    --cc=hramamurthy@google.com \
    --cc=joshwash@google.com \
    --cc=junfeng.guo@intel.com \
    --cc=rushilg@google.com \
    --cc=stable@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