linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Shakeel Butt <shakeelb@google.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Feng Tang <feng.tang@intel.com>,
	Michael Larabel <Michael@michaellarabel.com>
Cc: Linux MM <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: memcg: infrastructure to flush memcg stats
Date: Thu, 16 Sep 2021 13:44:44 -0700	[thread overview]
Message-ID: <CAHk-=wgcPrGW1=A9XetuUZv_QHf1p7znUUGbm7UCcawbboxRCQ@mail.gmail.com> (raw)
In-Reply-To: <64b88941-9ec0-8552-d05d-6503497f6f9d@MichaelLarabel.com>

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@michaellarabel.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/
>

  parent reply	other threads:[~2021-09-16 20:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 15:07 [memcg] 0f12156dff: will-it-scale.per_process_ops -33.6% regression kernel test robot
2021-09-07 15:46 ` Jens Axboe
2021-09-07 15:57   ` Shakeel Butt
2021-09-07 16:14     ` Jens Axboe
2021-09-07 16:39   ` Linus Torvalds
2021-09-07 16:43     ` Jens Axboe
2021-09-07 17:11       ` Roman Gushchin
2021-09-07 17:14         ` Tejun Heo
2021-09-07 17:18           ` Jens Axboe
2021-09-07 17:20             ` Tejun Heo
2021-09-07 17:31           ` Roman Gushchin
2021-09-07 17:48             ` Shakeel Butt
2021-09-07 19:42               ` Roman Gushchin
2021-09-08  8:13                 ` Vasily Averin
2021-09-07 16:49     ` Shakeel Butt
2021-09-07 17:52       ` Linus Torvalds
2021-09-07 18:19         ` Shakeel Butt
2021-09-07 18:33         ` Linus Torvalds
     [not found]           ` <64b88941-9ec0-8552-d05d-6503497f6f9d@MichaelLarabel.com>
2021-09-16 20:44             ` Linus Torvalds [this message]
2021-09-16 21:04               ` memcg: infrastructure to flush memcg stats Shakeel Butt

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='CAHk-=wgcPrGW1=A9XetuUZv_QHf1p7znUUGbm7UCcawbboxRCQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=Michael@michaellarabel.com \
    --cc=akpm@linux-foundation.org \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=shakeelb@google.com \
    --subject='Re: memcg: infrastructure to flush memcg stats' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).