Linux block layer
 help / color / mirror / Atom feed
From: Yang Erkun <yangerkun@huawei.com>
To: axboe@kernel.dk, josef@toxicpanda.com, xiubli@redhat.com,
	prasanna.kalever@redhat.com, ming.lei@redhat.com, yukuai@fygo.io,
	nilay@linux.ibm.com
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
	yangerkun@huawei.com, wangkefeng.wang@huawei.com,
	leijitang@huawei.com, yi.zhang@huawei.com,
	chengzhihao1@huawei.com, houtao1@huawei.com, wozizhi@huawei.com
Subject: [RFC PATCH 5/5] nbd: allow genetlink operations to run in parallel
Date: Sat,  7 Nov 2026 14:46:29 +0800	[thread overview]
Message-ID: <20261107064629.4093489-6-yangerkun@huawei.com> (raw)
In-Reply-To: <20261107064629.4093489-1-yangerkun@huawei.com>

Each nbd doit only touches one device's state, and the global state
(nbd_index_idr and nbd_total_devices) is accessed briefly under
nbd_index_mutex.  genl_mutex nevertheless serializes the whole genetlink
doit path.

The cost that matters is teardown: nbd_disconnect_and_put() calls
flush_workqueue() while holding genl_mutex, so a disconnect blocks every
other device for the duration of the flush.  Enable parallel_ops; the
preceding patches make sure no handler relies on genl_mutex for
correctness.

Test with a minimal netlink client in an 8-vCPU KVM guest, 32 devices x
10 connect/disconnect cycles, median of 3 runs:

  parallel_ops=0:  378 ms
  parallel_ops=1:   27 ms

Connect-only and status do not improve, since their critical sections
are short.

Suggested-by: Xiu Jianfeng <xiujianfeng@huawei.com>
Assisted-by: LLM
Signed-off-by: Yang Erkun <yangerkun@huawei.com>
---
 drivers/block/nbd.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index cf2a47fc572d..6a7060773e27 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -2542,6 +2542,7 @@ static struct genl_family nbd_genl_family __ro_after_init = {
 	.hdrsize	= 0,
 	.name		= NBD_GENL_FAMILY_NAME,
 	.version	= NBD_GENL_VERSION,
+	.parallel_ops	= 1,
 	.module		= THIS_MODULE,
 	.small_ops	= nbd_connect_genl_ops,
 	.n_small_ops	= ARRAY_SIZE(nbd_connect_genl_ops),
-- 
2.52.0


  parent reply	other threads:[~2026-11-07  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  6:46 [RFC PATCH 0/5] nbd: allow parallel genetlink operations Yang Erkun
2026-11-07  6:46 ` [RFC PATCH 1/5] nbd: validate the backend identifier under config_lock Yang Erkun
2026-11-07  6:46 ` [RFC PATCH 2/5] nbd: decrement nbd_total_devices when a device is removed Yang Erkun
2026-11-07  6:46 ` [RFC PATCH 3/5] nbd: publish devices atomically Yang Erkun
2026-11-07  6:46 ` [RFC PATCH 4/5] nbd: hold config_lock while updating nr_hw_queues Yang Erkun
2026-11-07  6:46 ` Yang Erkun [this message]
2026-11-17  4:36 ` [RFC PATCH 0/5] nbd: allow parallel genetlink operations yangerkun

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=20261107064629.4093489-6-yangerkun@huawei.com \
    --to=yangerkun@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=chengzhihao1@huawei.com \
    --cc=houtao1@huawei.com \
    --cc=josef@toxicpanda.com \
    --cc=leijitang@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nbd@other.debian.org \
    --cc=nilay@linux.ibm.com \
    --cc=prasanna.kalever@redhat.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=wozizhi@huawei.com \
    --cc=xiubli@redhat.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai@fygo.io \
    /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