From: Joshua Washington <joshwash@google.com>
To: netdev@vger.kernel.org
Cc: Joshua Washington <joshwash@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Praveen Kaligineedi <pkaligineedi@google.com>,
Ziwei Xiao <ziweixiao@google.com>,
John Fraker <jfraker@google.com>,
Matt Olson <maolson@google.com>, Bailey Forrest <bcf@google.com>,
Tim Hostetler <thostet@google.com>,
Jordan Rhee <jordanrhee@google.com>,
linux-kernel@vger.kernel.org, Max Yuan <maxyuan@google.com>
Subject: [PATCH net-next 0/2] gve: Support larger ring sizes in DQO-QPL mode
Date: Fri, 6 Feb 2026 17:17:31 -0800 [thread overview]
Message-ID: <20260207011734.437205-1-joshwash@google.com> (raw)
From: Max Yuan <maxyuan@google.com>
This patch series updates the gve driver to improve Queue Page List (QPL)
management and enable support for larger ring sizes when using the DQO-QPL
queue format.
Previously, the driver used hardcoded multipliers to determine the number
of pages to register for QPLs (e.g., 2x ring size for RX). This rigid
approach made it difficult to support larger ring sizes without potentially
exceeding the "max_registered_pages" limit reported by the device.
The first patch introduces a unified and flexible logic for calculating QPL
page requirements. It balances TX and RX page allocations based on the
configured ring sizes and scales the total count down proportionally if it
would otherwise exceed the device's global registration limit.
The second patch leverages this new flexibility to stop ignoring the
maximum ring size supported by the device in DQO-QPL mode. Users can now
configure ring sizes up to the device-reported maximum, as the driver will
automatically adjust the QPL size to stay within allowed memory bounds.
Matt Olson (2):
gve: Update QPL page registration logic
gve: Enable reading max ring size from the device in DQO-QPL mode
drivers/net/ethernet/google/gve/gve.h | 18 ++++++--------
drivers/net/ethernet/google/gve/gve_adminq.c | 18 ++++----------
drivers/net/ethernet/google/gve/gve_buffer_mgmt_dqo.c | 2 +-
drivers/net/ethernet/google/gve/gve_main.c | 40 ++++++++++++++++++++++++++++++++
drivers/net/ethernet/google/gve/gve_rx.c | 5 +---
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 6 ++---
drivers/net/ethernet/google/gve/gve_tx.c | 5 +---
drivers/net/ethernet/google/gve/gve_tx_dqo.c | 4 +---
8 files changed, 57 insertions(+), 41 deletions(-)
--
2.53.0.239.g8d8fc8a987-goog
next reply other threads:[~2026-02-07 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 1:17 Joshua Washington [this message]
2026-02-07 1:17 ` [PATCH net-next 1/2] gve: Update QPL page registration logic Joshua Washington
2026-02-11 9:34 ` Paolo Abeni
2026-02-13 21:43 ` kernel test robot
2026-02-07 1:17 ` [PATCH net-next 2/2] gve: Enable reading max ring size from the device in DQO-QPL mode 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=20260207011734.437205-1-joshwash@google.com \
--to=joshwash@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcf@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jfraker@google.com \
--cc=jordanrhee@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maolson@google.com \
--cc=maxyuan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=thostet@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@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