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>,
	hannes@cmpxchg.org, 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 06:51:41 -1000	[thread overview]
Message-ID: <aDCnnd46qjAvoxZq@slm.duckdns.org> (raw)
In-Reply-To: <CACSyD1P+wuSP2jhMsLHBAXDxGoBkWzK54S5BRzh63yby4g0OHw@mail.gmail.com>

Hello,

On Fri, May 23, 2025 at 11:35:57PM +0800, Zhongkun He wrote:
> > Is this something you want on the whole machine? If so, would global cgroup
> > mount option work?
> 
> It doesn't apply to the whole machine. It is only relevant to the pod with
> huge pages, where the service will be unavailable for over ten seconds if
> modify the cpuset.mems. Therefore, it would be ideal if there were an
> option to disable the migration for this special case.

I suppose we can add back an interface similar to cgroup1 but can you detail
the use case a bit? If you relocate threads without relocating memory, you'd
be paying on-going cost for memory access. It'd be great if you can
elaborate why such mode of operation is desirable.

Thanks.

-- 
tejun

  reply	other threads:[~2025-05-23 16:51 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 [this message]
2025-05-24  1:10               ` Zhongkun He
2025-05-24  1:14                 ` Tejun Heo
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=aDCnnd46qjAvoxZq@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.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.