From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
josef@toxicpanda.com, linux-block@vger.kernel.org,
nbd@other.debian.org
Subject: nbd: please don't spawn 16 threads when nbd is not even in use
Date: Tue, 22 Nov 2022 12:56:41 +0100 [thread overview]
Message-ID: <Y3y4+QqOlF00X9ET@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
Hi!
I see this... and it looks like there are 16 workqueues before nbd is
even used. Surely there are better ways to do that?
Best regards,
Pavel
257 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd0-recv
260 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd1-recv
263 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd2-recv
266 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd3-recv
269 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd4-recv
272 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd5-recv
275 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd6-recv
278 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd7-recv
281 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd8-recv
284 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd9-recv
287 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd10-recv
290 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd11-recv
293 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd12-recv
296 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd13-recv
299 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd14-recv
302 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nbd15-recv
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2022-11-22 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 11:56 Pavel Machek [this message]
2022-11-23 20:09 ` nbd: please don't spawn 16 threads when nbd is not even in use Eric Blake
2022-11-23 22:01 ` Pavel Machek
2022-11-24 1:17 ` Yu Kuai
2022-11-24 10:06 ` Pavel Machek
2022-11-24 11:17 ` Yu Kuai
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=Y3y4+QqOlF00X9ET@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.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