All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wei Hu" <weh@linux.microsoft.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v8 3/4] net: mana: support concurrent HWC requests
Date: Sat, 17 Oct 2026 12:06:46 +0000	[thread overview]
Message-ID: <sashiko-outbox-175501@kernel.org> (raw)
In-Reply-To: <983b5719644379806ac278b45cfb7cb70d2935f6.1791998462.git.weh@linux.microsoft.com>

> From: Long Li <longli@microsoft.com>
> 
> Give HWC message slots separate sender and response ownership. Initialize
> each slot under the inflight resource and per-slot locks, publish its
> bitmap bit last, and return its admission permit after both references are
> released. The per-slot lock also excludes an older duplicate callback from
> resetting or consuming the next caller's state.
> 
> 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.
> The bootstrap channel remains depth one here; the next patch negotiates
> and allocates larger queues.
> 
> Return -EBUSY for healthy admission pressure, but preserve -ETIMEDOUT when
> [ ... ]
> Link: https://lore.kernel.org/r/20260908035201.402424-4-longli@microsoft.com
> Link: https://lore.kernel.org/r/20260914175044.2a26bb46@kernel.org
> Link: https://lore.kernel.org/r/179196575640.434549.9102950927041409151@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.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1791998462.git.weh@linux.microsoft.com?part=3


  reply	other threads:[~2026-10-17 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 12:06 [PATCH net-next v8 0/4] net: mana: concurrent HWC requests and dynamic queue depth 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-17 12:06   ` sashiko-bot
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-17 12:06   ` sashiko-bot
2026-10-16 12:06 ` [PATCH net-next v8 3/4] net: mana: support concurrent HWC requests Wei Hu
2026-10-17 12:06   ` sashiko-bot [this message]
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-17 12:06   ` 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-175501@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.