linux-kernel - Re: memcg: infrastructure to flush memcg stats

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-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wgcPrGW1=A9XetuUZv_QHf1p7znUUGbm7UCcawbboxRCQ@mail.gmail.com>
Date:   Thu, 16 Sep 2021 13:44:44 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Shakeel Butt <shakeelb@...gle.com>,
        Marek Szyprowski <m.szyprowski@...sung.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Feng Tang <feng.tang@...el.com>,
        Michael Larabel <Michael@...haellarabel.com>
Cc:     Linux MM <linux-mm@...ck.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: memcg: infrastructure to flush memcg stats

So the kernel test robot complained about this commit back when it was
in the -mm tree:

  https://lore.kernel.org/all/20210726022421.GB21872@xsang-OptiPlex-9020/

but I never really saw anything else about it, and left it alone.

However, now Michael Larabel (of phoronix) points to this commit too,
and says it regresses several of his benchmarks too.

Shakeel, are you looking at this? Based on previous experience,
Michael is great at running benchmarks on patches that you come up
with.

           Linus

On Thu, Sep 16, 2021 at 2:55 AM Michael Larabel
<Michael@...haellarabel.com> wrote:
>
> Are you still looking at aa48e47e3906 around performance regressions[1]?
>
> With 5.15-rc1 on multiple systems I am seeing timed software compilation
> tests regressing compared to 5.14. A variety of different software
> builds are all slowing down by several percent when running on a 5.15
> kernel. The bisect led back to aa48e47e3906 as the first bad commit. I
> can't seem to find any discussions around that patch in more recent days
> so figured I'd ping you in case something was missed.
>
> Thanks,
>
> Michael
>
> [1]
> https://lists.01.org/hyperkitty/list/lkp@lists.01.org/message/MS2J5FCYQD62W4E5LHHPWC7YH7TWKUSV/
>