From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API
Date: Thu, 27 Oct 2016 23:13:34 +0200 [thread overview]
Message-ID: <20161027211334.GO3102@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20161027200929.GB17657@htj.duckdns.org>
On Thu, Oct 27, 2016 at 04:09:29PM -0400, Tejun Heo wrote:
> Hello,
>
> (cc'ing Johannes)
>
> On Thu, Oct 27, 2016 at 10:29:01AM -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.
>
> Yeah, sure. Do we have some time on Mon evening? I'm not sure I'll
> be around Tue evening.
I'll be in santa-fu all week. I figured if I'd go to the trouble of
dragging myself all the way to nowhere in the middle of NM, I might as
well stay there.
Godawful choice of location.
next prev parent reply other threads:[~2016-10-27 21:13 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
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 [this message]
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=20161027211334.GO3102@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.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