Re: [RFC 0/1] Try to add memory allocation info for cgroup oom kill

[Suren Baghdasaryan]

On Mon, Sep 8, 2025 at 12:08 PM Shakeel Butt <shakeel.butt@xxxxxxxxx> wrote:
>
> On Mon, Sep 08, 2025 at 10:51:30AM -0700, Suren Baghdasaryan wrote:
> > On Mon, Sep 8, 2025 at 10:49 AM Kent Overstreet
> > <kent.overstreet@xxxxxxxxx> wrote:
> > >
> > > On Mon, Sep 08, 2025 at 10:47:06AM -0700, Suren Baghdasaryan wrote:
> > > > On Mon, Sep 8, 2025 at 10:34 AM Kent Overstreet
> > > > <kent.overstreet@xxxxxxxxx> wrote:
> > > > >
> > > > > I think that got the memcg people looking at ways to make the accounting
> > > > > cheaper, but I'm not sure if anything landed from that.
> > > >
> > > > Yes, Roman landed a series of changes reducing the memcg accounting overhead.
> > >
> > > Do you know offhand how big that was?
> >
> > I'll need to dig it up but it was still much higher than memory profiling.
>
> What benchmark/workload was used to compare memcg accounting and memory
> profiling?

It was an in-kernel allocation stress test. Not very realistic but
good for comparing the overhead.