From: Simon Horman <horms@kernel.org>
To: Long Li <longli@microsoft.com>
Cc: Konstantin Taranov <kotaranov@microsoft.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/6] net: mana: Per-vPort EQ and MSI-X interrupt management
Date: Wed, 25 Mar 2026 16:56:46 +0000 [thread overview]
Message-ID: <20260325165646.GH111839@horms.kernel.org> (raw)
In-Reply-To: <20260323195952.1767304-1-longli@microsoft.com>
On Mon, Mar 23, 2026 at 12:59:46PM -0700, Long Li wrote:
> This series adds per-vPort Event Queue (EQ) allocation and MSI-X interrupt
> management for the MANA driver. Previously, all vPorts shared a single set
> of EQs. This change enables dedicated EQs per vPort with support for both
> dedicated and shared MSI-X vector allocation modes.
>
> Patch 1 moves EQ ownership from mana_context to per-vPort mana_port_context
> and exports create/destroy functions for the RDMA driver.
>
> Patch 2 adds device capability queries to determine whether MSI-X vectors
> should be dedicated per-vPort or shared. When the number of available MSI-X
> vectors is insufficient for dedicated allocation, the driver enables sharing
> mode with bitmap-based vector assignment.
>
> Patch 3 introduces the GIC (GDMA IRQ Context) abstraction with reference
> counting, allowing multiple EQs to safely share a single MSI-X vector.
>
> Patch 4 converts the global EQ allocation in probe/resume to use the new
> GIC functions.
>
> Patch 5 adds per-vPort GIC lifecycle management, calling get/put on each
> EQ creation and destruction during vPort open/close.
>
> Patch 6 extends the same GIC lifecycle management to the RDMA driver's EQ
> allocation path.
>
> Changes in v5:
> - Rebased on net-next/main
Hi Long Li,
Unfortunately v5 also doesn't apply cleanly to net-next.
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-03-25 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 19:59 [PATCH net-next v5 0/6] net: mana: Per-vPort EQ and MSI-X interrupt management Long Li
2026-03-23 19:59 ` [PATCH net-next v5 1/6] net: mana: Create separate EQs for each vPort Long Li
2026-03-23 19:59 ` [PATCH net-next v5 2/6] net: mana: Query device capabilities and configure MSI-X sharing for EQs Long Li
2026-03-23 19:59 ` [PATCH net-next v5 3/6] net: mana: Introduce GIC context with refcounting for interrupt management Long Li
2026-03-23 19:59 ` [PATCH net-next v5 4/6] net: mana: Use GIC functions to allocate global EQs Long Li
2026-03-23 19:59 ` [PATCH net-next v5 5/6] net: mana: Allocate interrupt context for each EQ when creating vPort Long Li
2026-03-23 19:59 ` [PATCH net-next v5 6/6] RDMA/mana_ib: Allocate interrupt contexts on EQs Long Li
2026-03-25 16:56 ` Simon Horman [this message]
2026-03-25 19:57 ` [EXTERNAL] Re: [PATCH net-next v5 0/6] net: mana: Per-vPort EQ and MSI-X interrupt management Long Li
2026-03-25 20:47 ` Long Li
2026-03-26 17:19 ` Simon Horman
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=20260325165646.GH111839@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.