From: Jakub Kicinski <kuba@kernel.org>
To: Joshua Washington <joshwash@google.com>,
Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, Ankit Garg <nktgrg@google.com>
Subject: Re: [PATCH net-next 0/3] gve: Improve RX buffer length management
Date: Thu, 23 Oct 2025 17:12:46 -0700 [thread overview]
Message-ID: <20251023171246.78bea1d8@kernel.org> (raw)
In-Reply-To: <20251022182301.1005777-1-joshwash@google.com>
On Wed, 22 Oct 2025 11:22:22 -0700 Joshua Washington wrote:
> This patch series improves the management of the RX buffer length for
> the DQO queue format in the gve driver. The goal is to make RX buffer
> length config more explicit, easy to change, and performant by default.
I suppose this was done in prep for later buffers for ZC?
It's less urgent given the change of plans in
https://lore.kernel.org/all/20251016184031.66c92962@kernel.org/
but still relevant AFAICT. Just wanted to confirm.. Mina?
next prev parent reply other threads:[~2025-10-24 0:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 18:22 [PATCH net-next 0/3] gve: Improve RX buffer length management Joshua Washington
2025-10-22 18:22 ` [PATCH net-next 1/3] gve: Decouple header split from RX buffer length Joshua Washington
2025-10-22 18:22 ` [PATCH net-next 2/3] gve: Allow ethtool to configure rx_buf_len Joshua Washington
2025-10-24 0:14 ` Jakub Kicinski
2025-10-24 18:17 ` Ankit Garg
2025-10-24 20:10 ` Jakub Kicinski
2025-10-24 20:14 ` Ankit Garg
2025-11-05 18:31 ` Ankit Garg
2025-10-22 18:22 ` [PATCH net-next 3/3] gve: Default to max_rx_buffer_size for DQO if device supported Joshua Washington
2025-10-24 0:12 ` Jakub Kicinski [this message]
2025-10-24 2:40 ` [PATCH net-next 0/3] gve: Improve RX buffer length management Mina Almasry
2025-10-24 17:31 ` Ankit Garg
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=20251023171246.78bea1d8@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=joshwash@google.com \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.