All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Zhongkun He <hezhongkun.hzk@bytedance.com>
Cc: Waiman Long <llong@redhat.com>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	muchun.song@linux.dev
Subject: Re: [External] Re: [PATCH] cpuset: introduce non-blocking cpuset.mems setting option
Date: Fri, 23 May 2025 15:14:08 -1000	[thread overview]
Message-ID: <aDEdYIEpu_7o6Kot@slm.duckdns.org> (raw)
In-Reply-To: <CACSyD1OWe-PkUjmcTtbYCbLi3TrxNQd==-zjo4S9X5Ry3Gwbzg@mail.gmail.com>

Hello,

On Sat, May 24, 2025 at 09:10:21AM +0800, Zhongkun He wrote:
...
> We move the task by modifying the cpuset.cpus and cpuset.mems and
> the memory migration is an option with cpuset.memory_migrate
> interface in V1. After we relocate the threads, the memory will be
> migrated by syscall move_pages in userspace slowly, within a few
> minutes.
> 
> Presently, cpuset.mems triggers synchronous memory migration,
> leading to prolonged and unacceptable service downtime in V2.
> 
> So we hope to add back an interface similar to cgroup v1, optional
> the migration.

Ah, I see, so it's not that you aren't migrating the memory but more that
the migration through cpuset.mems is too aggressive and causes disruption.
Is that the right understanding?

If so, would an interface to specify the rate of migration be a better
interface?

Thanks.

-- 
tejun

  reply	other threads:[~2025-05-24  1:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  3:15 [PATCH] cpuset: introduce non-blocking cpuset.mems setting option Zhongkun He
2025-05-20 13:13 ` kernel test robot
2025-05-20 13:25 ` kernel test robot
2025-05-20 13:34 ` Waiman Long
2025-05-21  2:35   ` [External] " Zhongkun He
2025-05-21 17:14     ` Tejun Heo
2025-05-22  3:37       ` Zhongkun He
2025-05-22 19:03         ` Tejun Heo
2025-05-23 15:35           ` Zhongkun He
2025-05-23 16:51             ` Tejun Heo
2025-05-24  1:10               ` Zhongkun He
2025-05-24  1:14                 ` Tejun Heo [this message]
2025-05-24  2:09                   ` Zhongkun He
2025-05-27 19:04                     ` Tejun Heo
2025-06-17 12:40                 ` Michal Koutný
2025-06-18  2:46                   ` Zhongkun He
2025-06-18  9:04                     ` Michal Koutný
2025-06-19  3:49                       ` Zhongkun He
2025-06-19 12:10                         ` Michal Koutný
2025-06-24  8:11                           ` Zhongkun He
2025-07-01  8:16                             ` Michal Koutný

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aDEdYIEpu_7o6Kot@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hezhongkun.hzk@bytedance.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=muchun.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.