From: Joshua Washington <joshwash@google.com>
Cc: dev@dpdk.org, Joshua Washington <joshwash@google.com>
Subject: [PATCH 0/7] net/gve: Tx datapath fixes for GVE DQO
Date: Mon, 7 Jul 2025 16:18:04 -0700 [thread overview]
Message-ID: <20250707231812.1937260-1-joshwash@google.com> (raw)
There are a number of consistency errors with the DQO Tx datapath, which
this series aims to address. These changes should make the driver much
more resilient against edge case and malformed packets overall.
Joshua Washington (7):
net/gve: send whole packet when mbuf is large
net/gve: clean when there are insufficient Tx descs
net/gve: don't write zero-length descriptors
net/gve: validate Tx packet before sending
net/gve: add DQO Tx descriptor limit
net/gve: fix DQO TSO descriptor limit
net/gve: clear DQO Tx descriptors before writing
.mailmap | 1 +
drivers/net/gve/gve_ethdev.c | 1 +
drivers/net/gve/gve_ethdev.h | 1 +
drivers/net/gve/gve_tx_dqo.c | 164 ++++++++++++++++++++++++++++++-----
4 files changed, 143 insertions(+), 24 deletions(-)
--
2.50.0.727.gbf7dc18ff4-goog
next reply other threads:[~2025-07-07 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 23:18 Joshua Washington [this message]
2025-07-07 23:18 ` [PATCH 1/7] net/gve: send whole packet when mbuf is large Joshua Washington
2025-07-07 23:18 ` [PATCH 2/7] net/gve: clean when there are insufficient Tx descs Joshua Washington
2025-07-07 23:18 ` [PATCH 3/7] net/gve: don't write zero-length descriptors Joshua Washington
2025-07-07 23:18 ` [PATCH 4/7] net/gve: validate Tx packet before sending Joshua Washington
2025-07-07 23:18 ` [PATCH 5/7] net/gve: add DQO Tx descriptor limit Joshua Washington
2025-07-07 23:18 ` [PATCH 6/7] net/gve: fix DQO TSO " Joshua Washington
2025-07-07 23:18 ` [PATCH 7/7] net/gve: clear DQO Tx descriptors before writing Joshua Washington
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=20250707231812.1937260-1-joshwash@google.com \
--to=joshwash@google.com \
--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 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).