From: Jakub Kicinski <kuba@kernel.org>
To: Wei Hu <weh@linux.microsoft.com>
Cc: longli@kernel.org, kotaranov@microsoft.com, davem@davemloft.net,
pabeni@redhat.com, edumazet@google.com, andrew+netdev@lunn.ch,
jgg@ziepe.ca, leon@kernel.org, haiyangz@microsoft.com,
wei.liu@kernel.org, decui@microsoft.com,
shradhagupta@linux.microsoft.com, horms@kernel.org,
ernis@linux.microsoft.com, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
gargaditya@linux.microsoft.com, kees+treewide@kernel.org,
kees@kernel.org, mawasthi@linux.microsoft.com, weh@microsoft.com,
edumazet@kernel.org
Subject: Re: [PATCH net-next v9 0/4] net: mana: concurrent HWC requests and dynamic queue depth
Date: Thu, 22 Oct 2026 08:23:33 -0700 [thread overview]
Message-ID: <20261022082333.5a259426@kernel.org> (raw)
In-Reply-To: <cover.1792679388.git.weh@linux.microsoft.com>
On Thu, 22 Oct 2026 15:02:58 +0000 Wei Hu wrote:
> This four-patch series adds concurrent HWC request ownership and
> PF-directed HWC queue depth to MANA. It starts with depth-one bootstrap
> queues and keeps setup private until the final channel is tested.
## Form letter - net-next-closed
The merge window for Linux v7.4 has begun, and the net-next
tree is now closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens. There is some uncertainty
about how long this merge window will last, so please check
https://netdev.bots.linux.dev/net-next.html
before reposting. net-next _may_ reopen on Nov 2nd.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
pv-bot: closed
next prev parent reply other threads:[~2026-10-22 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:02 [PATCH net-next v9 0/4] net: mana: concurrent HWC requests and dynamic queue depth Wei Hu
2026-10-22 15:02 ` [PATCH net-next v9 1/4] net: mana: prepare HWC ownership for safe reinitialization Wei Hu
2026-10-22 15:15 ` sashiko-bot
2026-10-22 15:03 ` [PATCH net-next v9 2/4] net: mana: give each HWC message slot its own completion state Wei Hu
2026-10-22 15:15 ` sashiko-bot
2026-10-22 15:03 ` [PATCH net-next v9 3/4] net: mana: support concurrent HWC requests Wei Hu
2026-10-22 15:15 ` sashiko-bot
2026-10-22 15:03 ` [PATCH net-next v9 4/4] net: mana: add dynamic HWC queue depth with reinit path Wei Hu
2026-10-22 15:15 ` sashiko-bot
2026-10-22 15:23 ` Jakub Kicinski [this message]
2026-10-25 8:06 ` [EXTERNAL] Re: [PATCH net-next v9 0/4] net: mana: concurrent HWC requests and dynamic queue depth Wei Hu
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=20261022082333.5a259426@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=ernis@linux.microsoft.com \
--cc=gargaditya@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kees+treewide@kernel.org \
--cc=kees@kernel.org \
--cc=kotaranov@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@kernel.org \
--cc=mawasthi@linux.microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=weh@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.