[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zr5WmpgJUXe79dcz@google.com>
Date: Thu, 15 Aug 2024 19:27:22 +0000
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Muchun Song <muchun.song@...ux.dev>,
"T . J . Mercier" <tjmercier@...gle.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Meta kernel team <kernel-team@...a.com>, cgroups@...r.kernel.org
Subject: Re: [PATCH v2 0/4] memcg: initiate deprecation of v1 features
On Wed, Aug 14, 2024 at 03:00:17PM -0700, Shakeel Butt wrote:
> Let start the deprecation process of the memcg v1 features which we
> discussed during LSFMMBPF 2024 [1]. For now add the warnings to collect
> the information on how the current users are using these features. Next
> we will work on providing better alternatives in v2 (if needed) and
> fully deprecate these features.
>
> Link: https://lwn.net/Articles/974575 [1]
>
> Shakeel Butt (4):
> memcg: initiate deprecation of v1 tcp accounting
> memcg: initiate deprecation of v1 soft limit
> memcg: initiate deprecation of oom_control
> memcg: initiate deprecation of pressure_level
I have a hope that we can deprecate memcg v1 altogether, but having more
information about specific v1 users won't hurt.
Acked-by: Roman Gushchin <roman.gushchin@...ux.dev>
Thanks!
Powered by blists - more mailing lists