From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andy Lutomirski <luto@amacapital.net>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API
Date: Thu, 27 Oct 2016 10:39:41 -0700 [thread overview]
Message-ID: <1477589981.3431.29.camel@HansenPartnership.com> (raw)
In-Reply-To: <CALCETrV17Eqxa9-ronb_C0xX5usWyzQo6dW_OKaBT+roSr+kaA@mail.gmail.com>
On Thu, 2016-10-27 at 10:29 -0700, Andy Lutomirski wrote:
> Would it make sense to have a session to try to resolve the current
> cgroup v2 API disagreement?
>
> In the interest of brevity, I'm not going to rehash the issues here,
> but in extremely short summary, they include tasks in non-leaf
> cgroups as well as whether threads in the same process can be in
> different cgroups.
We could do it later on Tuesday, that way it might be possible to
include more of the containers crowd than are going to KS.
James
next prev parent reply other threads:[~2016-10-27 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 17:29 Andy Lutomirski
2016-10-27 17:39 ` James Bottomley [this message]
2016-10-27 17:45 ` Josh Triplett
2016-10-27 20:09 ` Tejun Heo
2016-10-27 20:11 ` Paul Turner
2016-10-27 21:13 ` Peter Zijlstra
2016-10-30 23:50 ` Theodore Ts'o
2016-10-31 17:41 ` Rik van Riel
2016-10-30 15:27 ` Serge E. Hallyn
2016-10-30 23:41 ` Theodore Ts'o
2016-10-31 3:39 ` James Bottomley
2016-10-31 15:04 ` Serge E. Hallyn
2016-10-31 15:19 ` Tejun Heo
2016-10-31 17:06 ` Theodore Ts'o
2016-10-31 17:33 ` Tejun Heo
2016-10-31 17:35 ` James Bottomley
2016-11-01 13:33 ` James Bottomley
2016-10-31 17:40 ` Serge E. Hallyn
2016-10-31 17:42 ` Stéphane Graber
2016-10-31 23:00 ` Christian Brauner
2016-10-31 15:28 ` James Bottomley
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=1477589981.3431.29.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--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