From: Christian Brauner <christian.brauner@canonical.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Waiman Long" <longman@redhat.com>,
"Li Zefan" <lizefan@huawei.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
"Stéphane Graber" <stgraber@ubuntu.com>,
"Serge Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH] cpuset: Allow cpuset controller in default hierarchy
Date: Fri, 25 Aug 2017 00:58:58 +0200 [thread overview]
Message-ID: <20170824225857.ihxvcpgawb4fxda2@gmail.com> (raw)
In-Reply-To: <20170824150222.GQ491396@devbig577.frc2.facebook.com>
On Thu, Aug 24, 2017 at 08:02:22AM -0700, Tejun Heo wrote:
> Hello,
>
> On Thu, Aug 24, 2017 at 10:56:21AM -0400, Waiman Long wrote:
> > The main reason for sending out this patch is to figure out what exactly
> > is in your mind before enabling cpuset in v2.
> >
> > From my point of view, the exclusive setting makes cpuset behave more
> > like a resource domain that a resource allocated to one cgroup won't be
> > available for another cgroup. So we can argue it both ways whether it
> > violates the basic hierarchy rules or not.
>
> It's not even siblings interfering with other siblings. The resource
> knobs belong to the parent, right? So, the only thing it's doing is
> restricting the parent itself from creating certain configurations,
> which can be argued to be a feature but it's a really weird policy
> enforcement implemented in kernel.
>
> > I will be in the Plumbers Conference next month and we can talk more
> > about this. My goal is to make cgroup v2 ready for prime time hopefully
> > by the end of the year.
Hi,
I've been following this thread and the cpuset controller being enabled on
cgroup v2 is a really important step. As one of many container runtime
maintainers this is obviously a big step for us with a lot of impact. It'd be
really nice if we could have a little little discussion just to see what the
plan is like and what sort of features are going to expose to userspace. This is
all a very rapid development which is good. I'd just like to make sure to know
what we're in for. Sort of like what we did last year at Plumber but less
offical and without microphones and the overhead of having hundreds of people in
the room. :) Also it likely be way more relaxed given that a lot of the problems
dicussed back then seem to have been resolved.
CCing Serge and Stéphane. :)
Thanks!
Christian
>
> Sure, the only thing I think we need for cpuset is cutting down the
> interface to the minimal set which provides all the features to
> userspace.
>
> Thanks.
>
> --
> tejun
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-24 22:58 UTC|newest]
Thread overview: 7+ 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
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
[not found] ` <20170824150222.GQ491396-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2017-08-24 15:27 ` Waiman Long
2017-08-24 22:58 ` Christian Brauner [this message]
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=20170824225857.ihxvcpgawb4fxda2@gmail.com \
--to=christian.brauner@canonical.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=serge@hallyn.com \
--cc=stgraber@ubuntu.com \
--cc=tj@kernel.org \
/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