Message-ID: <CAJD7tkYQReWVG5f-xX8Lr7Yj0ewz4TFkN7uTe6Kkn8LDmp1zXQ@mail.gmail.com>
Date:   Tue, 1 Feb 2022 14:10:18 -0800
From:   Yosry Ahmed <yosryahmed@...gle.com>
To:     Johannes Weiner <hannes@...xchg.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Michal Hocko <mhocko@...nel.org>,
        Muchun Song <songmuchun@...edance.com>,
        Shakeel Butt <shakeelb@...gle.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] memcg: add per-memcg total kernel memory stat

Hello Johannes,

Thanks so much for your review.

On Tue, Feb 1, 2022 at 1:00 PM Johannes Weiner <hannes@...xchg.org> wrote:
>
> Hello Yosry,
>
> On Tue, Feb 01, 2022 at 08:08:23PM +0000, Yosry Ahmed wrote:
> > Currently memcg stats show several types of kernel memory:
> > kernel stack, page tables, sock, vmalloc, and slab.
> > However, there are other allocations with __GFP_ACCOUNT
> > (or supersets such as GFP_KERNEL_ACCOUNT) that are not accounted
> > in any of those stats, a few examples are:
> > - various kvm allocations (e.g. allocated pages to create vcpus)
> > - io_uring
> > - tmp_page in pipes during pipe_write()
> > - bpf ringbuffers
> > - unix sockets
> >
> > Keeping track of the total kernel memory is essential for the ease of
> > migration from cgroup v1 to v2 as there are large discrepancies between
> > v1's kmem.usage_in_bytes and the sum of the available kernel memory stats
> > in v2. Adding separate memcg stats for all __GFP_ACCOUNT kernel
> > allocations is an impractical maintenance burden as there a lot of those
> > all over the kernel code, with more use cases likely to show up in the
> > future.
>
> No objection, I'm just curious how it makes migration to v2 easier in
> particular. Or is it just that you've used the v1 stat to track
> application regressions and would like to continue doing that in v2?
>

We are using "memory.kmem.usage_in_bytes" in v1 to get the total
kernel memory accounted to a memcg to maintain historical data of jobs
memory (anon, file, kernel), and for debugging purposes. In v2 there
is no equivalent.

We found that the total of other existing v2 kernel memory stats
(vmalloc, slab, stack, ..) is very different for some workloads
compared to v1's "memory.kmem.usage_in_bytes". We need a v2 indicator
of the total kernel memory accounted to a memcg."

> > Therefore, add a "kernel" memcg stat that is analogous to kmem
> > page counter, with added benefits such as using rstat infrastructure
> > which aggregates stats more efficiently. Additionally, this provides a
> > lighter alternative in case the legacy kmem is deprecated in the future
> >
> > Signed-off-by: Yosry Ahmed <yosryahmed@...gle.com>
> > ---
> >  Documentation/admin-guide/cgroup-v2.rst |  5 +++++
> >  include/linux/memcontrol.h              |  1 +
> >  mm/memcontrol.c                         | 24 ++++++++++++++++++------
> >  3 files changed, 24 insertions(+), 6 deletions(-)
> >
> > diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> > index 5aa368d165da..a0027d570a7f 100644
> > --- a/Documentation/admin-guide/cgroup-v2.rst
> > +++ b/Documentation/admin-guide/cgroup-v2.rst
> > @@ -1317,6 +1317,11 @@ PAGE_SIZE multiple when read back.
> >         vmalloc (npn)
> >               Amount of memory used for vmap backed memory.
> >
> > +       kernel (npn)
> > +             Amount of total kernel memory, including
> > +             (kernel_stack, pagetables, percpu, vmalloc, slab) in
> > +             addition to other kernel memory use cases.
> > +
> >         shmem
> >               Amount of cached filesystem data that is swap-backed,
> >               such as tmpfs, shm segments, shared anonymous mmap()s
> > diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> > index b72d75141e12..fa51986365a4 100644
> > --- a/include/linux/memcontrol.h
> > +++ b/include/linux/memcontrol.h
> > @@ -34,6 +34,7 @@ enum memcg_stat_item {
> >       MEMCG_SOCK,
> >       MEMCG_PERCPU_B,
> >       MEMCG_VMALLOC,
> > +     MEMCG_KMEM,
> >       MEMCG_NR_STAT,
> >  };
> >
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 09d342c7cbd0..c55d7056ac98 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -1376,6 +1376,7 @@ static const struct memory_stat memory_stats[] = {
> >       { "percpu",                     MEMCG_PERCPU_B                  },
> >       { "sock",                       MEMCG_SOCK                      },
> >       { "vmalloc",                    MEMCG_VMALLOC                   },
> > +     { "kernel",                     MEMCG_KMEM                      },
>
> It's a superset of percpu, sock, vmalloc etc., so please move it ahead
> of them.
>
>         anon
>         file
>         kernel
>         kernel_stack
>         pagetables
>         ...
>
> and in the doc as well.
>

Done in v2.

> >       { "shmem",                      NR_SHMEM                        },
> >       { "file_mapped",                NR_FILE_MAPPED                  },
> >       { "file_dirty",                 NR_FILE_DIRTY                   },
> > @@ -2979,6 +2980,19 @@ static void memcg_free_cache_id(int id)
> >       ida_simple_remove(&memcg_cache_ida, id);
> >  }
> >
> > +static void mem_cgroup_kmem_record(struct mem_cgroup *memcg,
> > +                                int nr_pages)
>
> No real need for the namespace prefix since it's a static
> function. How about account_kmem()? Avoids the line wrap, too.

Does memcg_account_kmem() sound good? It avoids the line wrap too and
is more consistent with most static functions in the file that have
either a "memcg_" or "mem_cgroup_" prefix.

Thanks!

>
> Otherwise, looks good to me, so with those changes:
>
> Acked-by: Johannes Weiner <hannes@...xchg.org>
>
> Thanks!

Powered by blists - more mailing lists