linux-kernel - Re: [PATCH] blk-mq: add module parameter to not run block kworker on isolated CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZShPS46jgVsaBGHY@slm.duckdns.org>
Date:   Thu, 12 Oct 2023 09:55:55 -1000
From:   Tejun Heo <tj@...nel.org>
To:     Ming Lei <ming.lei@...hat.com>
Cc:     Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org, Juri Lelli <juri.lelli@...hat.com>,
        Andrew Theurer <atheurer@...hat.com>,
        Joe Mario <jmario@...hat.com>,
        Sebastian Jug <sejug@...hat.com>,
        Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH] blk-mq: add module parameter to not run block kworker on
 isolated CPUs

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