From: Stephen Hemminger <stephen@networkplumber.org>
To: Joshua Washington <joshwash@google.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/4] net/gve: out of order completion processing for DQO
Date: Tue, 26 Aug 2025 07:20:02 -0700 [thread overview]
Message-ID: <20250826072002.449ce90c@hermes.local> (raw)
In-Reply-To: <20250826000337.3922883-1-joshwash@google.com>
On Mon, 25 Aug 2025 17:03:33 -0700
Joshua Washington <joshwash@google.com> wrote:
> Both RX and TX processing on DQ were originally implemented with the
> asusmption that descriptor completions will be written by the hardware
> in the order that they are posted. In certain cases, such as RSC on RX
> and double completions on TX, this will not necessarily be the case.
>
> Depends-on: series-35656 ("net/gve: Tx datapath fixes for GVE DQO")
>
> Joshua Washington (4):
> net/gve: free Rx mbufs if allocation fails on ring setup
> net/gve: add datapath-specific logging for gve
> net/gve: support for out of order completions on DQ Tx
> net/gve: support for out of order completions on DQ Rx
>
> drivers/net/gve/base/gve_adminq.c | 2 +-
> drivers/net/gve/gve_ethdev.h | 20 ++-
> drivers/net/gve/gve_logs.h | 3 +
> drivers/net/gve/gve_rx_dqo.c | 135 +++++++++++-----
> drivers/net/gve/gve_tx_dqo.c | 250 ++++++++++++++++++------------
> 5 files changed, 267 insertions(+), 143 deletions(-)
>
Queued to next-net
prev parent reply other threads:[~2025-08-26 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:03 Joshua Washington
2025-08-26 0:03 ` [PATCH 1/4] net/gve: free Rx mbufs if allocation fails on ring setup Joshua Washington
2025-08-26 0:03 ` [PATCH 2/4] net/gve: add datapath-specific logging for gve Joshua Washington
2025-08-26 0:03 ` [PATCH 3/4] net/gve: support for out of order completions on DQ Tx Joshua Washington
2025-08-26 0:03 ` [PATCH 4/4] net/gve: support for out of order completions on DQ Rx Joshua Washington
2025-08-26 14:20 ` Stephen Hemminger [this message]
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=20250826072002.449ce90c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=joshwash@google.com \
/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).