mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Dmitry Shmidt <dimitrysh@google.com>,
	Amit Pundir <amit.pundir@linaro.org>,
	kernel-team@android.com, jsbarnes@google.com,
	sonnyrao@google.com, vpillai@digitalocean.com,
	peterz@infradead.org, Guenter Roeck <groeck@chromium.org>,
	Waiman Long <longman@redhat.com>, Greg Kerr <kerrnel@google.com>,
	cgroups@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
	Li Zefan <lizefan@huawei.com>
Subject: Re: [PATCH RFC] cpuset: Make cpusets get restored on hotplug
Date: Thu, 26 Mar 2020 15:44:48 -0400	[thread overview]
Message-ID: <20200326194448.GA133524@google.com> (raw)
In-Reply-To: <20200326192035.GO162390@mtj.duckdns.org>

Hi Tejun,

On Thu, Mar 26, 2020 at 03:20:35PM -0400, Tejun Heo wrote:
> On Thu, Mar 26, 2020 at 03:16:23PM -0400, Joel Fernandes (Google) wrote:
> > This deliberately changes the behavior of the per-cpuset
> > cpus file to not be effected by hotplug. When a cpu is offlined,
> > it will be removed from the cpuset/cpus file. When a cpu is onlined,
> > if the cpuset originally requested that that cpu was part of the cpuset,
> > that cpu will be restored to the cpuset. The cpus files still
> > have to be hierachical, but the ranges no longer have to be out of
> > the currently online cpus, just the physically present cpus.
> 
> This is already the behavior on cgroup2 and I don't think we want to
> introduce this big a behavior change to cgroup1 cpuset at this point.

It is not really that big a change. Please go over the patch, we are not
changing anything with how ->cpus_allowed works and interacts with the rest
of the system and the scheduler. We have just introduced a new mask to keep
track of which CPUs were requested without them being affected by hotplug. On
CPU onlining, we restore the state of ->cpus_allowed as not be affected by
hotplug.

There's 3 companies that have this issue so that should tell you something.
We don't want to carry this patch forever. Many people consider the hotplug
behavior to be completely broken.

thanks,

 - Joel


  reply	other threads:[~2020-03-26 19:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 19:16 Joel Fernandes (Google)
2020-03-26 19:20 ` Tejun Heo
2020-03-26 19:44   ` Joel Fernandes [this message]
2020-03-26 19:48     ` Tejun Heo
2020-03-26 19:57     ` Waiman Long
2020-03-26 20:05       ` Sonny Rao
2020-03-26 20:18         ` Tejun Heo
2020-03-26 20:23           ` Joel Fernandes
2020-03-27  1:26             ` Waiman Long
2020-03-27  3:32               ` Joel Fernandes
2020-03-26 21:47         ` Waiman Long
2020-03-26 22:03           ` Sonny Rao
2021-10-26 23:58       ` Barry Song
2021-10-27  1:06         ` Waiman Long
2021-10-27  2:21           ` Barry Song
2021-10-27  2:35             ` Waiman Long
2021-10-27  2:42               ` Barry Song

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=20200326194448.GA133524@google.com \
    --to=joel@joelfernandes.org \
    --cc=amit.pundir@linaro.org \
    --cc=cgroups@vger.kernel.org \
    --cc=dimitrysh@google.com \
    --cc=groeck@chromium.org \
    --cc=hannes@cmpxchg.org \
    --cc=jsbarnes@google.com \
    --cc=kernel-team@android.com \
    --cc=kerrnel@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=longman@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sonnyrao@google.com \
    --cc=tj@kernel.org \
    --cc=vpillai@digitalocean.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

Powered by JetHome