[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aOaq07jS60mHYGBe@slm.duckdns.org>
Date: Wed, 8 Oct 2025 08:17:55 -1000
From: Tejun Heo <tj@...nel.org>
To: Matyas Hurtik <matyas.hurtik@...77.com>
Cc: Daniel Sedlak <daniel.sedlak@...77.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Jonathan Corbet <corbet@....net>,
Neal Cardwell <ncardwell@...gle.com>,
Kuniyuki Iwashima <kuniyu@...gle.com>,
David Ahern <dsahern@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Shakeel Butt <shakeel.butt@...ux.dev>,
Yosry Ahmed <yosry.ahmed@...ux.dev>, linux-mm@...ck.org,
netdev@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Muchun Song <muchun.song@...ux.dev>, cgroups@...r.kernel.org,
Michal Koutný <mkoutny@...e.com>
Subject: Re: [PATCH v5] memcg: expose socket memory pressure in a cgroup
On Wed, Oct 08, 2025 at 02:46:23PM +0200, Matyas Hurtik wrote:
> Hello,
> > I'm not against going 1) but let's not do a separate file for this. Can't
> > you do memory.stat.local?
>
> I can't find memory.stat.local, so should we create it and add the counter
> as an entry there?
Yes.
> Regarding the code, is there anything you would like us to improve? I had to
> rewrite it a bit
>
> because of the recent changes.
I think memcg guys will have much better idea on the actual code. Let's wait
for them to chime in.
Thanks.
--
tejun
Powered by blists - more mailing lists