From: Tejun Heo <tj@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Andrew Theurer <atheurer@redhat.com>,
Joe Mario <jmario@redhat.com>, Sebastian Jug <sejug@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH] blk-mq: add module parameter to not run block kworker on isolated CPUs
Date: Thu, 12 Oct 2023 09:55:55 -1000 [thread overview]
Message-ID: <ZShPS46jgVsaBGHY@slm.duckdns.org> (raw)
In-Reply-To: <ZSXuqZNsyjJk1FGX@fedora>
Hello,
On Wed, Oct 11, 2023 at 08:39:05AM +0800, Ming Lei wrote:
> I appreciate that any specific suggestions about dealing with isolated CPUs
> generically for bound WQ can be shared.
Oh, all I meant was whether we can at least collect this into or at least
adjacent to the existing housekeeping / isolcpu parameters. Let's say
there's someone who really wants to isolated some CPUs, how would they find
out the different parameters if they're scattered across different
subsystems?
Thanks.
--
tejun
next prev parent reply other threads:[~2023-10-12 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:22 [PATCH] blk-mq: add module parameter to not run block kworker on isolated CPUs Ming Lei
2023-10-10 18:45 ` Tejun Heo
2023-10-11 0:39 ` Ming Lei
2023-10-12 19:55 ` Tejun Heo [this message]
2023-10-13 2:01 ` Ming Lei
2023-10-13 11:26 ` Frederic Weisbecker
2023-10-13 12:23 ` Ming Lei
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=ZShPS46jgVsaBGHY@slm.duckdns.org \
--to=tj@kernel.org \
--cc=atheurer@redhat.com \
--cc=axboe@kernel.dk \
--cc=frederic@kernel.org \
--cc=jmario@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=sejug@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.