[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3jopfa5deuncuvfjltop7qu5dvdak37imdtmkjmnd5alg2zc2s@wiaztnxwgavz>
Date: Thu, 4 Sep 2025 16:30:32 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Chuyi Zhou <zhouchuyi@...edance.com>
Cc: tj@...nel.org, hannes@...xchg.org, longman@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] cpuset: Don't always flush cpuset_migrate_mm_wq in
cpuset_write_resmask
On Thu, Sep 04, 2025 at 03:45:03PM +0800, Chuyi Zhou <zhouchuyi@...edance.com> wrote:
> It is unnecessary to always wait for the flush operation of
> cpuset_migrate_mm_wq to complete in cpuset_write_resmask, as modifying
> cpuset.cpus or cpuset.exclusive does not trigger mm migrations. The
> flush_workqueue can be executed only when cpuset.mems is modified.
>
> Signed-off-by: Chuyi Zhou <zhouchuyi@...edance.com>
> ---
> kernel/cgroup/cpuset.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reasonable and AFAICT correct optimization.
Reviewed-by: Michal Koutný <mkoutny@...e.com>
Download attachment "signature.asc" of type "application/pgp-signature" (266 bytes)
Powered by blists - more mailing lists