mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: hramamurthy@google.com
Cc: netdev@vger.kernel.org, joshwash@google.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	sdf@fomichev.me, jordanrhee@google.com, willemb@google.com,
	nktgrg@google.com, maolson@google.com, thostet@google.com,
	jacob.e.keller@intel.com, debarghyak@google.com, kees@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next v9 09/12] gve: introduce new methods to handle IRQ doorbells
Date: Fri, 02 Oct 2026 10:06:37 +0000	[thread overview]
Message-ID: <179093559726.434549.2118678373272356755@kernel.org> (raw)
In-Reply-To: <20260930190428.1130007-10-hramamurthy@google.com>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The commit message of "gve: introduce new methods to handle IRQ
  doorbells" claims more than the code does and leaves out several…

--

gve: introduce new methods to handle IRQ doorbells

This commit adds request_db_info and release_db_resources callbacks to
struct gve_ctrl_ops. The AdminQ implementations issue the configure and
deconfigure device resources commands and set the per-block irq_db_index
pointers. Allocation of the irq_db_indices DMA buffer moves out of
gve_alloc_notify_blocks() into new helpers called from
gve_alloc_control_plane_resources().

> Admin Queue and Mailbox modes. All behaviors related to the IRQ doorbell
> indices will be managed by these new methods instead of occurring
> directly in notify_block setup/teardown methods.

[Severity: Low]

Is this description accurate for what the patch does?

gve_adminq_request_db_info() only sends the configure device resources
command, using the counter_array_bus and irq_db_indices_bus that are
already allocated. It then sets ntfy_blocks[i].irq_db_index.
gve_adminq_release_db_resources() only sends the deconfigure command.

The DMA buffer that holds the doorbell indices is allocated and freed by
two new static helpers in gve_main.c: gve_alloc_irq_db_indices() and
gve_free_irq_db_indices(). They are called from
gve_alloc_control_plane_resources() and gve_free_control_plane_resources(),
not from the new ops.

The next sentence says GQ ring counters will be managed in
request_db_info. However, the counter array is still allocated by
gve_alloc_counter_array() in gve_alloc_control_plane_resources().

The v3 changelog says this split was intentional. The "all behaviors"
wording looks like it is left over from the earlier design, even after the
v6 commit message update.

The commit message also leaves out a few other changes in the patch:

- gve_alloc_control_plane_resources() now allocates the counter array
  after the notify blocks and stats report, followed by irq_db_indices.
  gve_free_control_plane_resources() changes its free order to match.

- A new gve_ntfy_to_msix_idx() helper is now used for the msix_vectors[]
  lookups in gve_setup_notify_blocks() and gve_teardown_notify_blocks().
  The "Failed to receive msix vector" message now prints msix_idx.

- The "the last vector" and "the first n-1 vectors" comments are removed,
  although mgmt_msix_idx is still num_ntfy_blks.

None of these seem to change behavior in AdminQ mode. Could the commit
message be updated to match the code and mention these changes?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260930190428.1130007-1-hramamurthy%40google.com

  reply	other threads:[~2026-10-02 10:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 19:04 [PATCH net-next v9 00/12] gve: AdminQ mode related refactors Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 01/12] gve: add struct gve_device_info to hold device properties Harshitha Ramamurthy
2026-10-02 10:06   ` netdev-bot+sashiko
2026-09-30 19:04 ` [PATCH net-next v9 02/12] gve: introduce control plane operations structure Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 03/12] gve: introduce ctrl ops to set vectors and Qs Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 04/12] gve: introduce gve_adminq_get_device_properties() Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 05/12] gve: refactor gve_init_priv for reset path Harshitha Ramamurthy
2026-10-02 10:06   ` netdev-bot+sashiko
2026-09-30 19:04 ` [PATCH net-next v9 06/12] gve: simplify reset logic Harshitha Ramamurthy
2026-10-02 10:06   ` netdev-bot+sashiko
2026-09-30 19:04 ` [PATCH net-next v9 07/12] gve: add gve_ctrl_ops for gve initialization/teardown sequences Harshitha Ramamurthy
2026-10-02 10:06   ` netdev-bot+sashiko
2026-09-30 19:04 ` [PATCH net-next v9 08/12] gve: split up notify block allocation and setup paths Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 09/12] gve: introduce new methods to handle IRQ doorbells Harshitha Ramamurthy
2026-10-02 10:06   ` netdev-bot+sashiko [this message]
2026-09-30 19:04 ` [PATCH net-next v9 10/12] gve: setup and teardown management interrupts Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 11/12] gve: add ctrl ops for queue operations Harshitha Ramamurthy
2026-09-30 19:04 ` [PATCH net-next v9 12/12] gve: add link status/speed ctrl ops Harshitha Ramamurthy

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=179093559726.434549.2118678373272356755@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=debarghyak@google.com \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hramamurthy@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=jordanrhee@google.com \
    --cc=joshwash@google.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maolson@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nktgrg@google.com \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sdf@fomichev.me \
    --cc=thostet@google.com \
    --cc=willemb@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

all inboxes | Powered by JetHome®