All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuset: Allow cpuset controller in default hierarchy
Date: Thu, 24 Aug 2017 07:43:22 -0700	[thread overview]
Message-ID: <20170824144322.GP491396@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1503585611-13496-1-git-send-email-longman@redhat.com>

Hello, Waiman.

On Thu, Aug 24, 2017 at 10:40:11AM -0400, Waiman Long wrote:
> Given the fact that thread mode is now queued for 4.14, it is now
> time to enable cpuset to be used in the default hierarchy (cgroup v2)
> as it is clearly threaded.

I'm not sure we want things like exclusive settings in v2 as it
directly violates basic hierarchy rules (a sibling shouldn't be able
to affect what another sibling can or can't do).  We need to think
more about what should be exposed in v2.

Thanks.

-- 
tejun

  reply	other threads:[~2017-08-24 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 14:40 [PATCH] cpuset: Allow cpuset controller in default hierarchy Waiman Long
2017-08-24 14:43 ` Tejun Heo [this message]
2017-08-24 14:56   ` Waiman Long
2017-08-24 14:56     ` Waiman Long
     [not found]     ` <863b01d0-e724-dab6-258e-d5980f985938-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-24 15:02       ` Tejun Heo
2017-08-24 15:02         ` Tejun Heo
     [not found]         ` <20170824150222.GQ491396-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2017-08-24 15:27           ` Waiman Long
2017-08-24 15:27             ` Waiman Long
2017-08-24 22:58         ` Christian Brauner
2017-08-24 22:58           ` Christian Brauner
2017-08-24 17:33   ` Mike Galbraith
2017-08-24 17:33     ` Mike Galbraith

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=20170824144322.GP491396@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.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 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.