From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <jdamato@fastly.com>
Cc: netdev@vger.kernel.org, darinzon@amazon.com, akiyano@amazon.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
kheib@redhat.com, linux-kernel@vger.kernel.org,
ndagan@amazon.com, pabeni@redhat.com, saeedb@amazon.com,
shayagr@amazon.com
Subject: Re: [net-next v2 0/2] ena: Link IRQs, queues, and NAPI instances
Date: Thu, 03 Oct 2024 23:20:36 +0000 [thread overview]
Message-ID: <172799763674.2024724.12393925801122696226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241002001331.65444-1-jdamato@fastly.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Oct 2024 00:13:26 +0000 you wrote:
> Greetings:
>
> Welcome to v2. This includes only cosmetic changes, see changelog below
> and in each patch.
>
> 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] ena: Link IRQs to NAPI instances
https://git.kernel.org/netdev/net-next/c/989867846f7f
- [net-next,v2,2/2] ena: Link queues to NAPIs
https://git.kernel.org/netdev/net-next/c/888634377f8e
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-03 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 0:13 [net-next v2 0/2] ena: Link IRQs, queues, and NAPI instances Joe Damato
2024-10-02 0:13 ` [net-next v2 1/2] ena: Link IRQs to " Joe Damato
2024-10-02 6:27 ` Arinzon, David
2024-10-02 0:13 ` [net-next v2 2/2] ena: Link queues to NAPIs Joe Damato
2024-10-02 6:28 ` Arinzon, David
2024-10-02 6:28 ` [net-next v2 0/2] ena: Link IRQs, queues, and NAPI instances Arinzon, David
2024-10-03 23:20 ` 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=172799763674.2024724.12393925801122696226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kheib@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndagan@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.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