From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH] nvmet: make nvmet_wq unbound
Date: Mon, 6 May 2024 14:08:08 +0200 [thread overview]
Message-ID: <20240506120808.GA30005@lst.de> (raw)
In-Reply-To: <d15da519-2c81-42bb-8f60-89da4650f7a9@grimberg.me>
On Mon, May 06, 2024 at 10:50:02AM +0300, Sagi Grimberg wrote:
> It doesn't have any better justification. I never really saw any other
> justification
> to add WQ_SYSFS to a (usually unbound) workqueue, than simply have
> visibility
> or ability to control it.
>
> What makes you think this is not harmless and useful?
Because now we have to deal with users setting more or less insane
parameters on the workqueue.
next prev parent reply other threads:[~2024-05-06 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 10:39 [PATCH] nvmet: make nvmet_wq unbound Sagi Grimberg
2024-05-06 5:33 ` Christoph Hellwig
2024-05-06 7:50 ` Sagi Grimberg
2024-05-06 12:08 ` Christoph Hellwig [this message]
2024-05-06 14:05 ` Sagi Grimberg
2024-05-06 14:16 ` Christoph Hellwig
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=20240506120808.GA30005@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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