linux-kernel - Re: [PATCH blktests v3 09/12] common/fio: Limit number of random jobs

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: <99a6cc5f-31b2-787c-f448-53239a351ddd@nvidia.com>
Date:   Wed, 3 May 2023 09:41:37 +0000
From:   Chaitanya Kulkarni <chaitanyak@...dia.com>
To:     Daniel Wagner <dwagner@...e.de>,
        "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
        Chaitanya Kulkarni <chaitanyak@...dia.com>,
        Shin'ichiro Kawasaki <shinichiro@...tmail.com>,
        Hannes Reinecke <hare@...e.de>
Subject: Re: [PATCH blktests v3 09/12] common/fio: Limit number of random jobs

On 5/3/23 01:02, Daniel Wagner wrote:
> Limit the number of random threads to 32 for big machines. This still
> gives enough randomness but limits the resource usage.
>
> Signed-off-by: Daniel Wagner <dwagner@...e.de>
> ---

I don't think we should change this, the point of all the tests is
to not limit the resources but use threads at least equal to
$(nproc), see recent patches from lenovo they have 448 cores,
limiting 32 is < 10% CPUs and that is really small number for
a large machine if we decide to run tests on that machine ...

-ck