From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, saeedm@nvidia.com,
leon@kernel.org, mbloch@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
gal@nvidia.com, witu@nvidia.com, toke@redhat.com
Subject: Re: [PATCH net-next V2 0/4] net/mlx5e: Save per-channel async ICOSQ in default
Date: Mon, 19 Jan 2026 21:00:10 +0000 [thread overview]
Message-ID: <176885641079.136413.11790985486873558102.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1768376800-1607672-1-git-send-email-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Jan 2026 09:46:36 +0200 you wrote:
> Hi,
>
> This is V2, find V1 here:
> https://lore.kernel.org/all/1762939749-1165658-1-git-send-email-tariqt@nvidia.com/
>
> This series by William reduces the default number of SQs in a channel
> from 3 down to 2, by not creating the async ICOSQ (asynchronous
> internal-communication-operations send-queue).
>
> [...]
Here is the summary with links:
- [net-next,V2,1/4] net/mlx5e: Move async ICOSQ lock into ICOSQ struct
https://git.kernel.org/netdev/net-next/c/ea945f4f3991
- [net-next,V2,2/4] net/mlx5e: Use regular ICOSQ for triggering NAPI
https://git.kernel.org/netdev/net-next/c/56aca3e0f730
- [net-next,V2,3/4] net/mlx5e: Move async ICOSQ to dynamic allocation
https://git.kernel.org/netdev/net-next/c/1b080bd74840
- [net-next,V2,4/4] net/mlx5e: Conditionally create async ICOSQ
https://git.kernel.org/netdev/net-next/c/abed42f9cd80
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:[~2026-01-19 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 7:46 [PATCH net-next V2 0/4] net/mlx5e: Save per-channel async ICOSQ in default Tariq Toukan
2026-01-14 7:46 ` [PATCH net-next V2 1/4] net/mlx5e: Move async ICOSQ lock into ICOSQ struct Tariq Toukan
2026-01-14 7:46 ` [PATCH net-next V2 2/4] net/mlx5e: Use regular ICOSQ for triggering NAPI Tariq Toukan
2026-01-14 7:46 ` [PATCH net-next V2 3/4] net/mlx5e: Move async ICOSQ to dynamic allocation Tariq Toukan
2026-01-14 7:46 ` [PATCH net-next V2 4/4] net/mlx5e: Conditionally create async ICOSQ Tariq Toukan
2026-01-19 21:00 ` 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=176885641079.136413.11790985486873558102.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=toke@redhat.com \
--cc=witu@nvidia.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