From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: pkaligineedi@google.com, horms@kernel.org,
Joe Damato <jdamato@fastly.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Jeroen de Borst <jeroendb@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Shailend Chand <shailend@google.com>,
Willem de Bruijn <willemb@google.com>,
Ziwei Xiao <ziweixiao@google.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [net-next v2 0/2] gve: Link IRQs, queues, and NAPI instances
Date: Mon, 30 Sep 2024 21:07:06 +0000 [thread overview]
Message-ID: <20240930210731.1629-1-jdamato@fastly.com> (raw)
Greetings:
Welcome to v2. The previous revision was an RFC [1].
This series uses the netdev-genl API to link IRQs and queues to NAPI IDs
so that this information is queryable by user apps. This is particularly
useful for epoll-based busy polling apps which rely on having access to
the NAPI ID.
I've tested these commits on a GCP instance with a GVE NIC configured
and have included test output in the commit messages for each patch
showing how to query the information.
Thanks,
Joe
[1]: https://lore.kernel.org/netdev/20240926030025.226221-1-jdamato@fastly.com/
v2:
- Fixed spelling error in commit message of patch 1 suggested by Simon
Horman
- Fixed patch 2 to skip XDP TX queues, as suggested by Praveen
Kaligineedi
Joe Damato (2):
gve: Map IRQs to NAPI instances
gve: Map NAPI instances to queues
drivers/net/ethernet/google/gve/gve_main.c | 17 +++++++++++++++++
drivers/net/ethernet/google/gve/gve_utils.c | 1 +
2 files changed, 18 insertions(+)
--
2.43.0
next reply other threads:[~2024-09-30 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 21:07 Joe Damato [this message]
2024-09-30 21:07 ` [net-next v2 1/2] gve: Map IRQs to " Joe Damato
2024-10-01 15:38 ` Praveen Kaligineedi
2024-09-30 21:07 ` [net-next v2 2/2] gve: Map NAPI instances to queues Joe Damato
2024-10-01 15:37 ` Praveen Kaligineedi
2024-10-04 0:10 ` [net-next v2 0/2] gve: Link IRQs, queues, and NAPI instances patchwork-bot+netdevbpf
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=20240930210731.1629-1-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=shailend@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
all inboxes | Powered by JetHome®