From: patchwork-bot+netdevbpf@kernel.org
To: Erni Sri Satya Vennela <ernis@linux.microsoft.com>
Cc: haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, weh@microsoft.com,
kotaranov@microsoft.com, horms@kernel.org,
gargaditya@linux.microsoft.com, mawasthi@linux.microsoft.com,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
shradhagupta@linux.microsoft.com,
sahilchandna@linux.microsoft.com
Subject: Re: [PATCH net-next] net: mana: Allocate queue MSI-X vectors on demand
Date: Sat, 14 Nov 2026 03:30:04 +0000 [thread overview]
Message-ID: <179462700464.1971357.5494475799168934446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106063011.43293-1-ernis@linux.microsoft.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Nov 2026 22:30:11 -0800 you wrote:
> MANA allocates its entire MSI-X budget at probe time, even when the
> active event queues (EQs) use only a small part of it. With dynamic
> MSI-X, this budget can be num_online_cpus() + 1, leaving unused vectors
> that consume interrupt resources.
>
> Remove eager allocation of queue vectors and use mana_gd_get_gic(),
> which already allocates a vector when an EQ needs one. Keep the HWC
> interrupt available during device initialization.
>
> [...]
Here is the summary with links:
- [net-next] net: mana: Allocate queue MSI-X vectors on demand
https://git.kernel.org/netdev/net-next/c/6964ff21c5d8
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-11-14 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 6:30 [PATCH net-next] net: mana: Allocate queue MSI-X vectors on demand Erni Sri Satya Vennela
2026-11-10 14:15 ` netdev-bot+sashiko
2026-11-14 3:30 ` 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=179462700464.1971357.5494475799168934446.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@kernel.org \
--cc=ernis@linux.microsoft.com \
--cc=gargaditya@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mawasthi@linux.microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sahilchandna@linux.microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=weh@microsoft.com \
--cc=wei.liu@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.