linux-kernel - Re: [PATCH] backing_dev_info: introduce min_bw/max

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]

Date:   Fri, 18 Jun 2021 16:41:58 +0200
From:   Miklos Szeredi <miklos@...redi.hu>
To:     Michael Stapelberg <stapelberg+linux@...gle.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-mm <linux-mm@...ck.org>,
        linux-fsdevel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
        Dennis Zhou <dennis@...nel.org>, Jens Axboe <axboe@...nel.dk>,
        Roman Gushchin <guro@...com>,
        Johannes Thumshirn <johannes.thumshirn@....com>,
        Jan Kara <jack@...e.cz>, Song Liu <song@...nel.org>,
        David Sterba <dsterba@...e.com>
Subject: Re: [PATCH] backing_dev_info: introduce min_bw/max_bw limits

On Fri, 18 Jun 2021 at 10:31, Michael Stapelberg
<stapelberg+linux@...gle.com> wrote:

> Maybe, but I don’t have the expertise, motivation or time to
> investigate this any further, let alone commit to get it done.
> During our previous discussion I got the impression that nobody else
> had any cycles for this either:
> https://lore.kernel.org/linux-fsdevel/CANnVG6n=ySfe1gOr=0ituQidp56idGARDKHzP0hv=ERedeMrMA@mail.gmail.com/
>
> Have you had a look at the China LSF report at
> http://bardofschool.blogspot.com/2011/?
> The author of the heuristic has spent significant effort and time
> coming up with what we currently have in the kernel:
>
> """
> Fengguang said he draw more than 10K performance graphs and read even
> more in the past year.
> """
>
> This implies that making changes to the heuristic will not be a quick fix.

Having a piece of kernel code sitting there that nobody is willing to
fix is certainly not a great situation to be in.

And introducing band aids is not going improve the above situation,
more likely it will prolong it even further.

Thanks,
Miklos