[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241024065712.1274481-1-shakeel.butt@linux.dev>
Date: Wed, 23 Oct 2024 23:57:09 -0700
From: Shakeel Butt <shakeel.butt@...ux.dev>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Muchun Song <muchun.song@...ux.dev>,
Hugh Dickins <hughd@...gle.com>,
linux-mm@...ck.org,
cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org,
Meta kernel team <kernel-team@...a.com>
Subject: [RFC PATCH 0/3] memcg-v1: fully deprecate charge moving
The memcg v1's charge moving feature has been deprecated for almost 2
years and the kernel warns if someone try to use it. This warning has
been backported to all stable kernel and there have not been any report
of the warning or the request to support this feature anymore. Let's
proceed to fully deprecate this feature.
Shakeel Butt (3):
memcg-v1: fully deprecate move_charge_at_immigrate
memcg-v1: remove charge move code
memcg-v1: remove memcg move locking code
.../admin-guide/cgroup-v1/memory.rst | 82 +-
fs/buffer.c | 5 -
include/linux/memcontrol.h | 59 --
mm/filemap.c | 1 -
mm/memcontrol-v1.c | 960 +-----------------
mm/memcontrol-v1.h | 6 -
mm/memcontrol.c | 14 -
mm/page-writeback.c | 21 +-
mm/rmap.c | 1 -
mm/vmscan.c | 11 -
10 files changed, 8 insertions(+), 1152 deletions(-)
--
2.43.5
Powered by blists - more mailing lists