From: sashiko-bot@kernel.org
To: "Wei Hu" <weh@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v6 3/4] net: mana: support concurrent HWC requests
Date: Thu, 08 Oct 2026 12:54:04 +0000 [thread overview]
Message-ID: <sashiko-outbox-164180@kernel.org> (raw)
In-Reply-To: <e954bfad6e48734927d900458afc00aa0a9a2e69.1790670523.git.weh@linux.microsoft.com>
> From: Long Li <longli@microsoft.com>
>
> Replace the depth-one timeout latch with per-slot sender and response
> ownership. Initialize each slot under the inflight resource lock, publish
> its bitmap bit last, and release it only after both sides have finished.
> This preserves response-buffer withdrawal and timeout quarantine while
> allowing independent message IDs to make progress.
>
> Serialize SQ posting so concurrent senders cannot corrupt the producer
> state. A posted request which times out keeps its response reference and
> admission permit until its late response arrives or teardown cancels it.
>
> Return -EBUSY when all slots remain occupied. Admission pressure is not a
> response timeout and must not make callers start dead-channel recovery.
>
> [ ... ]
>
> Link: https://lore.kernel.org/r/20260908035201.402424-4-longli@microsoft.com
> Link: https://lore.kernel.org/r/20260914175044.2a26bb46@kernel.org
> Signed-off-by: Long Li <longli@microsoft.com>
> Signed-off-by: Wei Hu <weh@microsoft.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790665894.git.weh@linux.microsoft.com?part=3
next prev parent reply other threads:[~2026-10-08 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:53 [PATCH net-next v6 0/4] net: mana: concurrent HWC requests and dynamic queue depth Wei Hu
2026-10-07 12:53 ` [PATCH net-next v6 1/4] net: mana: prepare HWC ownership for safe reinitialization Wei Hu
2026-10-08 12:54 ` sashiko-bot
2026-10-09 11:20 ` Wei Hu
2026-10-07 12:53 ` [PATCH net-next v6 2/4] net: mana: give each HWC message slot its own completion state Wei Hu
2026-10-08 12:54 ` sashiko-bot
2026-10-07 12:53 ` [PATCH net-next v6 3/4] net: mana: support concurrent HWC requests Wei Hu
2026-10-08 12:54 ` sashiko-bot [this message]
2026-10-07 12:53 ` [PATCH net-next v6 4/4] net: mana: add dynamic HWC queue depth with reinit path Wei Hu
2026-10-08 12:54 ` sashiko-bot
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=sashiko-outbox-164180@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=weh@linux.microsoft.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