From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
"T . J . Mercier" <tjmercier@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>,
cgroups@vger.kernel.org
Subject: [PATCH v2 0/4] memcg: initiate deprecation of v1 features
Date: Wed, 14 Aug 2024 15:00:17 -0700 [thread overview]
Message-ID: <20240814220021.3208384-1-shakeel.butt@linux.dev> (raw)
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
Changes since v1:
- Fix build (T.J. Mercier)
- Fix documentation
.../admin-guide/cgroup-v1/memory.rst | 32 +++++++++++++++----
mm/memcontrol-v1.c | 16 ++++++++++
2 files changed, 42 insertions(+), 6 deletions(-)
--
2.43.5
next reply other threads:[~2024-08-14 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 22:00 Shakeel Butt [this message]
2024-08-14 22:00 ` [PATCH v2 1/4] memcg: initiate deprecation of v1 tcp accounting Shakeel Butt
2024-08-14 22:00 ` [PATCH v2 2/4] memcg: initiate deprecation of v1 soft limit Shakeel Butt
2024-08-14 22:57 ` T.J. Mercier
2024-08-14 22:00 ` [PATCH v2 3/4] memcg: initiate deprecation of oom_control Shakeel Butt
2024-08-14 22:58 ` T.J. Mercier
2024-08-14 23:47 ` Shakeel Butt
2024-08-14 22:00 ` [PATCH v2 4/4] memcg: initiate deprecation of pressure_level Shakeel Butt
2024-08-14 22:58 ` T.J. Mercier
2024-08-15 6:29 ` [PATCH v2 0/4] memcg: initiate deprecation of v1 features Michal Hocko
2024-08-15 19:27 ` Roman Gushchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240814220021.3208384-1-shakeel.butt@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tjmercier@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox