From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <jdamato@fastly.com>
Cc: netdev@vger.kernel.org, pkaligineedi@google.com,
horms@kernel.org, davem@davemloft.net, edumazet@google.com,
hramamurthy@google.com, kuba@kernel.org, jeroendb@google.com,
pabeni@redhat.com, shailend@google.com, willemb@google.com,
ziweixiao@google.com, linux-kernel@vger.kernel.org
Subject: Re: [net-next v2 0/2] gve: Link IRQs, queues, and NAPI instances
Date: Fri, 04 Oct 2024 00:10:32 +0000 [thread overview]
Message-ID: <172800063204.2038698.8514793410721572832.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240930210731.1629-1-jdamato@fastly.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Sep 2024 21:07:06 +0000 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] gve: Map IRQs to NAPI instances
https://git.kernel.org/netdev/net-next/c/3017238b60d3
- [net-next,v2,2/2] gve: Map NAPI instances to queues
https://git.kernel.org/netdev/net-next/c/021f9e671e4a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-04 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 21:07 Joe Damato
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 ` patchwork-bot+netdevbpf [this message]
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=172800063204.2038698.8514793410721572832.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jdamato@fastly.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®