From: sashiko-bot@kernel.org
To: "Wei Hu" <weh@linux.microsoft.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v7 2/4] net: mana: give each HWC message slot its own completion state
Date: Wed, 14 Oct 2026 08:06:26 +0000 [thread overview]
Message-ID: <sashiko-outbox-170993@kernel.org> (raw)
In-Reply-To: <b6a611e9de0f67b48ddde2948e257128df1e90fc.1791561995.git.weh@linux.microsoft.com>
> From: Long Li <longli@microsoft.com>
>
> Concurrent requests require the response handler and the waiting sender to
> agree on the lifetime and result state of each message slot.
>
> Protect the caller's output buffer, Linux error and device status with a
> per-slot lock. Publish the output buffer only while the sender is waiting
> and withdraw it before every return. A late response therefore cannot copy
> through a pointer to caller storage whose lifetime has ended.
>
> Reinitialize completion and result state when the slot is acquired. If
> the response records its result while the timed wait expires, return that
> result instead of reporting a false timeout.
>
> HWC responses contain only the slot ID. After a genuine timeout, prevent
> the serialized bootstrap channel from reusing that ID until teardown. This
> keeps a stale response from completing a later request before the next
> patch replaces the depth-one latch with per-slot sender and response
> ownership.
>
> Split response-status handling and request cleanup into helpers so the send
> path has structured returns rather than phase-jumping gotos.
>
> Link: https://lore.kernel.org/r/20260908035201.402424-3-longli@microsoft.com
> Link: https://lore.kernel.org/r/20260908035201.402424-4-longli@microsoft.com
> 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.1791561995.git.weh@linux.microsoft.com?part=2
next prev parent reply other threads:[~2026-10-14 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 8:05 [PATCH net-next v7 0/4] net: mana: concurrent HWC requests and dynamic queue depth Wei Hu
2026-10-13 8:05 ` [PATCH net-next v7 1/4] net: mana: prepare HWC ownership for safe reinitialization Wei Hu
2026-10-14 8:06 ` sashiko-bot
2026-10-13 8:05 ` [PATCH net-next v7 2/4] net: mana: give each HWC message slot its own completion state Wei Hu
2026-10-14 8:06 ` sashiko-bot [this message]
2026-10-13 8:05 ` [PATCH net-next v7 3/4] net: mana: support concurrent HWC requests Wei Hu
2026-10-14 8:06 ` sashiko-bot
2026-10-13 8:05 ` [PATCH net-next v7 4/4] net: mana: add dynamic HWC queue depth with reinit path Wei Hu
2026-10-14 8:06 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-10-14 8:15 [PATCH net-next v7 2/4] net: mana: give each HWC message slot its own completion state netdev-bot+sashiko
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-170993@kernel.org \
--to=sashiko-bot@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 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.