From: Wei Hu <weh@microsoft.com>
To: Jakub Kicinski <kuba@kernel.org>, Wei Hu <weh@linux.microsoft.com>
Cc: "longli@kernel.org" <longli@kernel.org>,
Konstantin Taranov <kotaranov@microsoft.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"leon@kernel.org" <leon@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
Dexuan Cui <DECUI@microsoft.com>,
"shradhagupta@linux.microsoft.com"
<shradhagupta@linux.microsoft.com>,
"horms@kernel.org" <horms@kernel.org>,
"ernis@linux.microsoft.com" <ernis@linux.microsoft.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gargaditya@linux.microsoft.com" <gargaditya@linux.microsoft.com>,
"kees+treewide@kernel.org" <kees+treewide@kernel.org>,
"kees@kernel.org" <kees@kernel.org>,
"mawasthi@linux.microsoft.com" <mawasthi@linux.microsoft.com>,
"edumazet@kernel.org" <edumazet@kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH net-next v8 0/4] net: mana: concurrent HWC requests and dynamic queue depth
Date: Thu, 22 Oct 2026 14:54:11 +0000 [thread overview]
Message-ID: <SE3P153MB1848ED8701A4CEC783EB2C2EBB652@SE3P153MB1848.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20261021134053.74169d5a@kernel.org>
Hi Jakub,
> -----Original Message-----
> From: Jakub Kicinski <kuba@kernel.org>
> On Fri, 16 Oct 2026 12:06:11 +0000 Wei Hu wrote:
> > This series adds concurrent HWC request ownership and negotiated HWC
> > queue depth to MANA. It starts from depth-one bootstrap queues, keeps
> > setup private until the final channel is tested, and preserves the
> > distinction between CPU lifetime and PF ownership of DMA mappings.
>
> Please respond to the netdev-bot AI review in a timely manner.
> (You can ignore the global review bot, it's not even CCed to netdev so
> maintainers don't actually see it :/)
>
> Can't tell at a glance whether the Medium / High severity issues are indeed
> valid or nit picks, but since the merge window has already started let's revisit
> this after. Please repost in 2 weeks.
> --
> pw-bot: defer
I just replied to netdev-bot about its review findings. Only couple issues in
patch 3 are valid. Rest of them are either pre-existing or nit picks. I will
send a v9 shortly.
Thanks,
Wei
PS: Thanks for letting me know that I can ignore the global review bot.
prev parent reply other threads:[~2026-10-22 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 12:06 Wei Hu
2026-10-16 12:06 ` [PATCH net-next v8 1/4] net: mana: prepare HWC ownership for safe reinitialization Wei Hu
2026-10-20 13:36 ` netdev-bot+sashiko
2026-10-22 14:44 ` Wei Hu
2026-10-16 12:06 ` [PATCH net-next v8 2/4] net: mana: give each HWC message slot its own completion state Wei Hu
2026-10-20 13:36 ` netdev-bot+sashiko
2026-10-22 14:44 ` Wei Hu
2026-10-16 12:06 ` [PATCH net-next v8 3/4] net: mana: support concurrent HWC requests Wei Hu
2026-10-20 13:36 ` netdev-bot+sashiko
2026-10-22 14:44 ` Wei Hu
2026-10-16 12:06 ` [PATCH net-next v8 4/4] net: mana: add dynamic HWC queue depth with reinit path Wei Hu
2026-10-20 13:36 ` netdev-bot+sashiko
2026-10-22 14:44 ` Wei Hu
2026-10-21 20:40 ` [PATCH net-next v8 0/4] net: mana: concurrent HWC requests and dynamic queue depth Jakub Kicinski
2026-10-22 14:54 ` Wei Hu [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=SE3P153MB1848ED8701A4CEC783EB2C2EBB652@SE3P153MB1848.APCP153.PROD.OUTLOOK.COM \
--to=weh@microsoft.com \
--cc=DECUI@microsoft.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--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=kuba@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®