[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABdmKX0kVYj6a8wntFoi1nZ0UfjKR9Y-oLfoOO_a_XhisuN-xg@mail.gmail.com>
Date: Wed, 28 Aug 2024 10:49:20 -0700
From: "T.J. Mercier" <tjmercier@...gle.com>
To: Kinsey Ho <kinseyho@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
Yosry Ahmed <yosryahmed@...gle.com>, Roman Gushchin <roman.gushchin@...ux.dev>,
Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>,
Shakeel Butt <shakeel.butt@...ux.dev>, Muchun Song <muchun.song@...ux.dev>,
Tejun Heo <tj@...nel.org>, Zefan Li <lizefan.x@...edance.com>, mkoutny@...e.com
Subject: Re: [PATCH mm-unstable v3 4/5] mm: restart if multiple traversals raced
On Tue, Aug 27, 2024 at 4:11 PM Kinsey Ho <kinseyho@...gle.com> wrote:
>
> Currently, if multiple reclaimers raced on the same position, the
> reclaimers which detect the race will still reclaim from the same memcg.
> Instead, the reclaimers which detect the race should move on to the next
> memcg in the hierarchy.
>
> So, in the case where multiple traversals race, jump back to the start
> of the mem_cgroup_iter() function to find the next memcg in the
> hierarchy to reclaim from.
>
> Signed-off-by: Kinsey Ho <kinseyho@...gle.com>
Reviewed-by: T.J. Mercier <tjmercier@...gle.com>
Powered by blists - more mailing lists