[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <isidrym2cm6qshx2t6v5vvatd7vmyrd7ve543rgy4ddx4csiej@x72hqvpkkwfi>
Date: Thu, 24 Oct 2024 18:33:26 -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>, Yosry Ahmed <yosryahmed@...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: Re: [PATCH v1 0/6] memcg-v1: fully deprecate charge moving
On Thu, Oct 24, 2024 at 06:22:57PM GMT, Shakeel Butt wrote:
> 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
>
Please ignore the patch at [1] as it was resent by mistake.
[1] https://lore.kernel.org/linux-mm/20241024065712.1274481-4-shakeel.butt@linux.dev
Powered by blists - more mailing lists