ACK: [SRU][R:linux-gcp][PATCH 0/2] Support larger gVNIC queue depth on Gen3+ GCE VMs

Ian Whitfield ian.whitfield at canonical.com
Fri Sep 11 15:27:15 UTC 2026


On 9/10/26 8:17 PM, Rickey Castillo via kernel-team wrote:
> BugLink: https://bugs.launchpad.net/bugs/2153950
>
> [Impact]
>
> Currently, the maximum queue depth supported for gVNIC on overcommitted Gen3+
> VMs such as N4 is 1K, whereas the maximum queue depth supported on Gen1/Gen2 VMs
> is 2K. Customers who are migrating their workloads from N2 to N4 have requested
> higher queue depth support on N4 VMs.
>
> [Fix]
>
> Target patches:
> a2f19184014f ("gve: Enable reading max ring size from the device in DQO-QPL mode")
> 07993df56091 ("gve: Update QPL page registration logic")
>
> Both applied cleanly.
>
> [Test Plan]
>
> The following output indicates the feature is missing:
>    $ sudo ethtool -G ens3 rx 4096
>    netlink error: Operation not supported
> So the test plan for Canonical was to confirm that `sudo ethtool -G ens3 rx
> 4096` exits successfully without an error.
>
> [Regression potential]
>
> This has low potential for regression because the commits applied cleanly,
> and only the two target patches were required.
>
> [Other]
>
> SF: 00433236 (for GCP variants)
> PIT: 509371317 (for GKE variants)
>
> Matt Olson (2):
>    gve: Enable reading max ring size from the device in DQO-QPL mode
>    gve: Update QPL page registration logic
>
>   drivers/net/ethernet/google/gve/gve.h         | 18 ++++----
>   drivers/net/ethernet/google/gve/gve_adminq.c  | 18 ++------
>   .../ethernet/google/gve/gve_buffer_mgmt_dqo.c |  2 +-
>   drivers/net/ethernet/google/gve/gve_main.c    | 41 +++++++++++++++++++
>   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, 58 insertions(+), 41 deletions(-)
Acked-by: Ian Whitfield <ian.whitfield at canonical.com>



More information about the kernel-team mailing list