[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aDYMzfYYSS8ly1Nt@slm.duckdns.org>
Date: Tue, 27 May 2025 09:04:45 -1000
From: Tejun Heo <tj@...nel.org>
To: Zhongkun He <hezhongkun.hzk@...edance.com>
Cc: Waiman Long <llong@...hat.com>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, muchun.song@...ux.dev,
Johannes Weiner <hannes@...xchg.org>
Subject: Re: [External] Re: [PATCH] cpuset: introduce non-blocking
cpuset.mems setting option
Hello,
On Sat, May 24, 2025 at 10:09:36AM +0800, Zhongkun He wrote:
> On Sat, May 24, 2025 at 9:14 AM Tejun Heo <tj@...nel.org> wrote:
> Per my understanding, the interface of migration rate is far more complex.
> To slow down the migration, moving it to the userspace can also help determine
> when to carry out this operation.
(cc'ing Johannes for mm)
The user interface can be pretty simple. It can just be an approximate
bandwidth of scan or migration, but yeah, I don't know whether this is going
to be too complex. Pacing migration from user side isn't trivial either,
tho. If this is something necessary, it'd be nice if kernel can provide
something relatively simple to use and can cover most usecases.
Johannes, what do you think?
Thanks.
--
tejun
Powered by blists - more mailing lists