Linux-HyperV List
 help / color / mirror / Atom feed
From: Wei Hu <weh@linux.microsoft.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-rdma@vger.kernel.org, linux-hyperv@vger.kernel.org,
	bpf@vger.kernel.org, netdev@vger.kernel.org, weh@microsoft.com,
	kuba@kernel.org
Subject: Re: [PATCH net-next v7 06/13] net: mana: swap queue sets in mana_set_priv_flags
Date: Tue, 20 Oct 2026 04:30:41 +0000	[thread overview]
Message-ID: <qset-v7-sashiko-06-v8-plan.20261018.weh@linux.microsoft.com> (raw)
In-Reply-To: <sashiko-outbox-175606@kernel.org>

Hi,

> Does this code introduce an open-coded trylock pattern?

I will keep the existing synchronization in v8. channel_changing is a
vport-admission reservation protected by vport_mutex, not an unprotected
replacement for the serialization of Ethernet reconfiguration.

RTNL serializes the Ethernet reconfiguration and reset writers. The
reservation remains set while the rebuild releases vport_mutex between
individual vport operations, so concurrent RDMA admission through
mana_cfg_vport(check=true) can reject that interval under vport_mutex.
The success and failure cleanup paths clear the reservation under the
same mutex.

Holding vport_mutex over the whole rebuild is not a drop-in replacement:
the vport configuration/unconfiguration helpers acquire it themselves.
The report does not identify a missing exclusion edge in the existing
protocol, which is also present in v6. I am not redesigning that protocol
solely on the basis of its resemblance to a trylock.

Thanks,
Wei

  reply	other threads:[~2026-10-20  4:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 15:38 [PATCH net-next v7 00/13] net: mana: reconfigure by replacing the queue set Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 01/13] net: mana: add queue-set allocation and teardown helpers Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 02/13] net: mana: share the EQ pool across a queue-set swap Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 03/13] net: mana: keep per-queue statistics in the port context Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 04/13] net: mana: swap queue sets in mana_set_channels Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 05/13] net: mana: swap queue sets in mana_set_ringparam Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 06/13] net: mana: swap queue sets in mana_set_priv_flags Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu [this message]
2026-10-16 15:38 ` [PATCH net-next v7 07/13] net: mana: swap queue sets in mana_change_mtu Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 08/13] net: mana: swap queue sets in mana_xdp_set Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 09/13] net: mana: do not bail out of mana_detach on dealloc failure Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 10/13] net: mana: release EQs left idle by a channel-count reduction Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 11/13] net: mana: keep a user-configured RSS table across a queue rebuild Wei Hu
2026-10-17 15:39   ` sashiko-bot
2026-10-20  4:30     ` Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 12/13] net: mana: keep the surviving queues when the channel count is reduced Wei Hu
2026-10-16 15:38 ` [PATCH net-next v7 13/13] net: mana: keep the existing queues when the channel count is raised Wei Hu
2026-10-18 12:35 ` [PATCH net-next v7 00/13] net: mana: reconfigure by replacing the queue set Leon Romanovsky

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=qset-v7-sashiko-06-v8-plan.20261018.weh@linux.microsoft.com \
    --to=weh@linux.microsoft.com \
    --cc=bpf@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=weh@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