From: Yang Erkun <yangerkun@huawei.com>
To: josef@toxicpanda.com, axboe@kernel.dk, hch@lst.de, yukuai@kernel.org
Cc: yi.zhang@huawei.com, chengzhihao1@huawei.com,
echo.chenlin@huawei.com, leo.lilong@huaweicloud.com,
wangkefeng.wang@huawei.com, yangerkun@huawei.com,
linux-block@vger.kernel.org, nbd@other.debian.org
Subject: [PATCH v3 0/6] nbd: eliminate queue freeze/unfreeze overhead in connection setup
Date: Mon, 13 Jul 2026 14:56:38 +0800 [thread overview]
Message-ID: <20260713065644.1637594-1-yangerkun@huawei.com> (raw)
This series eliminates the blk_mq_freeze_queue()/unfreeze_queue()
overhead that currently occurs during nbd connection setup(nbd provide
ondemand and was using in AI sandbox e2b[1] to mount and attach rootfs).
Each freeze cycle will introduce a RCU grace which was significant
with multi-core system.
time nbd-client --name myexport --connections 96 127.0.0.1 1234
After this patchset:
real 0m0.090s
user 0m0.004s
sys 0m0.018s
Without this patchset:
real 0m2.195s
user 0m0.005s
sys 0m0.022s
v2->v3:
1. Stop using xarray, and protect it by rejecting late NBD_SET_SOCKS
2. Eliminate freeze in nbd_set_size when device setup
3. Add module parameter to eliminate freeze for pre-created device
v1->v2:
1. Rewrite cover letter
2. Eliminate freeze call from blk_mq_update_nr_hw_queues in
nbd_start_device for netlink path
[1]. https://github.com/e2b-dev/e2b
Long Li (1):
nbd: simplify find_fallback() by removing redundant logic
Yang Erkun (5):
nbd: disallow NBD_SET_SOCK on an active device
nbd: remove queue freeze in nbd_add_socket
nbd: set nr_hw_queues at device creation to skip queue freeze
nbd: skip queue freeze when setting size at device startup
nbd: add nr_hw_queues module parameter for pre-created devices
drivers/block/nbd.c | 119 ++++++++++++++++++++++++++++----------------
1 file changed, 76 insertions(+), 43 deletions(-)
--
2.52.0
next reply other threads:[~2026-07-13 7:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 6:56 Yang Erkun [this message]
2026-07-13 6:56 ` [PATCH v3 1/6] nbd: simplify find_fallback() by removing redundant logic Yang Erkun
2026-07-13 6:56 ` [PATCH v3 2/6] nbd: disallow NBD_SET_SOCK on an active device Yang Erkun
2026-07-22 3:03 ` yu kuai
2026-07-22 6:12 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 3/6] nbd: remove queue freeze in nbd_add_socket Yang Erkun
2026-07-22 3:17 ` yu kuai
2026-07-22 6:35 ` yu kuai
2026-07-22 8:45 ` yangerkun
2026-07-22 9:20 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 4/6] nbd: set nr_hw_queues at device creation to skip queue freeze Yang Erkun
2026-07-22 3:38 ` yu kuai
2026-07-23 1:09 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 5/6] nbd: skip queue freeze when setting size at device startup Yang Erkun
2026-07-22 3:49 ` yu kuai
2026-07-23 1:22 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 6/6] nbd: add nr_hw_queues module parameter for pre-created devices Yang Erkun
2026-07-22 3:53 ` yu kuai
2026-07-23 1:24 ` yangerkun
2026-07-21 8:41 ` [PATCH v3 0/6] nbd: eliminate queue freeze/unfreeze overhead in connection setup 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=20260713065644.1637594-1-yangerkun@huawei.com \
--to=yangerkun@huawei.com \
--cc=axboe@kernel.dk \
--cc=chengzhihao1@huawei.com \
--cc=echo.chenlin@huawei.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=leo.lilong@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=wangkefeng.wang@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai@kernel.org \
/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