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: Thu, 22 May 2025 09:03:22 -1000 [thread overview]
Message-ID: <aC90-jGtD_tJiP5K@slm.duckdns.org> (raw)
In-Reply-To: <CACSyD1MvwPT7i5_PnEp32seeb7X_svdCeFtN6neJ0=QPY1hDsw@mail.gmail.com>
Hello,
On Thu, May 22, 2025 at 11:37:44AM +0800, Zhongkun He wrote:
> > I don't think this is a good idea. O_NONBLOCK means "don't wait", not "skip
> > this".
>
> Yes, I agree. However, we have been experiencing this issue for a long time,
> so we hope to have an option to disable memory migration in v2.
>
> Would it be possible to re-enable the memory.migrate interface and
> disable memory migration by default in v2?
>
> Alternatively, could we introduce an option in cpuset.mems to explicitly
> indicate that memory migration should not occur?
>
> Please feel free to share any suggestions you might have.
Is this something you want on the whole machine? If so, would global cgroup
mount option work?
Thanks.
--
tejun
next prev parent reply other threads:[~2025-05-22 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 3:15 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 [this message]
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
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=aC90-jGtD_tJiP5K@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®