[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <gbqumqkxixvvrbbqh55rw6thgfa67tw2kkcuauc4xj5t6pnivd@3yfkokngo43w>
Date: Mon, 10 Jul 2023 16:44:53 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Ivan Babrou <ivan@...udflare.com>
Cc: cgroups@...r.kernel.org, Linux MM <linux-mm@...ck.org>,
kernel-team <kernel-team@...udflare.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Shakeel Butt <shakeelb@...gle.com>,
Muchun Song <muchun.song@...ux.dev>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Expensive memory.stat + cpu.stat reads
Hello.
On Fri, Jun 30, 2023 at 04:22:28PM -0700, Ivan Babrou <ivan@...udflare.com> wrote:
> As you might've noticed from the output, splitting the loop into two
> makes the code run 10x faster.
That is curious.
> We're running Linux v6.1 (the output is from v6.1.25) with no patches
> that touch the cgroup or mm subsystems, so you can assume vanilla
> kernel.
Have you watched for this on older kernels too?
> I am happy to try out patches or to do some tracing to help understand
> this better.
I see in your reproducer you tried swapping order of controllers
flushed.
Have you also tried flushing same controller twice (in the inner loop)?
(Despite the expectation is that it shouldn't be different from half the
scenario where ran two loops.)
Thanks,
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists