[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ps3ld3lvabkdonldljtscmq5kgvwk4zr6qxwxmy2v4sibv6hl5@xohjmnrqgmpe>
Date: Fri, 20 Jun 2025 12:19:58 -0700
From: Shakeel Butt <shakeel.butt@...ux.dev>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>, Johannes Weiner <hannes@...xchg.org>,
Marco Crivellari <marco.crivellari@...e.com>, Michal Hocko <mhocko@...nel.org>, Michal Hocko <mhocko@...e.com>,
Muchun Song <muchun.song@...ux.dev>, Peter Zijlstra <peterz@...radead.org>,
Roman Gushchin <roman.gushchin@...ux.dev>, Tejun Heo <tj@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Vlastimil Babka <vbabka@...e.cz>, Waiman Long <longman@...hat.com>
Subject: Re: [PATCH 05/27] memcg: Prepare to protect against concurrent
isolated cpuset change
On Fri, Jun 20, 2025 at 05:22:46PM +0200, Frederic Weisbecker wrote:
> The HK_TYPE_DOMAIN housekeeping cpumask will soon be made modifyable at
> runtime. In order to synchronize against memcg workqueue to make sure
> that no asynchronous draining is pending or executing on a newly made
> isolated CPU, read-lock the housekeeping rwsem lock while targeting
> and queueing a drain work.
>
> Whenever housekeeping will update the HK_TYPE_DOMAIN cpumask, a memcg
> workqueue flush will also be issued in a further change to make sure
> that no work remains pending after a CPU had been made isolated.
>
> Signed-off-by: Frederic Weisbecker <frederic@...nel.org>
Acked-by: Shakeel Butt <shakeel.butt@...ux.dev>
Powered by blists - more mailing lists