mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "haifeng.xu" <haifeng.xu@shopee.com>,
	lizefan.x@bytedance.com, hannes@cmpxchg.org,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: Optimize update_tasks_nodemask()
Date: Wed, 23 Nov 2022 08:54:37 -1000	[thread overview]
Message-ID: <Y35sbREgYE6aIdIp@slm.duckdns.org> (raw)
In-Reply-To: <5fccf438-fdbe-1bc8-6460-b3911cc51566@redhat.com>

On Wed, Nov 23, 2022 at 01:48:46PM -0500, Waiman Long wrote:
> I think it is an issue anyway if different threads of a process are in
> different cpusets with different node mask. It is not a configuration that
> should be used at all.

Anything memory related is in the same boat and people still use them
reaching whatever end results they reach. Given the whole thing is pretty
ill-defined, I don't wanna change the behavior now.

> This patch makes update_tasks_nodemask() somewhat similar to cpuset_attach()
> where all tasks are iterated to update the node mask but only the task
> leaders are required to update the mm. For a non-group leader task, maybe we
> can check if the group leader is in the same cpuset. If so, we can skip the
> mm update. Do we need similar change in cpuset_attach()?

The leader isn't special tho. We just wanna avoid visiting the same mm more
than once, right?

Thanks.

-- 
tejun

  reply	other threads:[~2022-11-23 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  8:21 haifeng.xu
2022-11-23 17:05 ` Tejun Heo
2022-11-23 18:48   ` Waiman Long
2022-11-23 18:54     ` Tejun Heo [this message]
2022-11-23 19:05       ` Waiman Long
2022-11-23 19:07         ` Tejun Heo
2022-11-23 20:23 ` Waiman Long
2022-11-24  3:33   ` Haifeng Xu
2022-11-24  4:24     ` Waiman Long
2022-11-24  7:49       ` Haifeng Xu
2022-11-24 23:00         ` Waiman Long
2022-11-25  2:14           ` Haifeng Xu
2022-11-28  7:34           ` Haifeng Xu

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=Y35sbREgYE6aIdIp@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=haifeng.xu@shopee.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    /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®