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. Changes since RFC: - Writing 0 to memory.move_charge_at_immigrate is allowed. - Remove the memcg move locking in separate patches. Shakeel Butt (6): memcg-v1: fully deprecate move_charge_at_immigrate memcg-v1: remove charge move code memcg-v1: no need for memcg locking for dirty tracking memcg-v1: no need for memcg locking for writeback tracking memcg-v1: no need for memcg locking for MGLRU 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 | 958 +----------------- mm/memcontrol-v1.h | 6 - mm/memcontrol.c | 14 - mm/page-writeback.c | 20 +- mm/rmap.c | 1 - mm/vmscan.c | 11 - 10 files changed, 8 insertions(+), 1149 deletions(-) -- 2.43.5
