From: Tejun Heo <tj@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Daniel Lezcano" <daniel.lezcano@free.fr>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Li Zefan" <lizf@cn.fujitsu.com>,
"Aditya Kali" <adityakali@google.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Max Kellermann" <mk@cm4all.com>,
"Tim Hockin" <thockin@hockin.org>,
"Glauber Costa" <glommer@gmail.com>,
"Paul Menage" <paul@paulmenage.org>,
"Daniel J Walsh" <dwalsh@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Oleg Nesterov" <oleg@redhat.com>,
"Mandeep Singh Baines" <msb@chromium.org>,
Cgroups <cgroups@vger.kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
Containers <containers@lists.linux-foundation.org>,
"Papp Tamás" <tompos@martos.bme.hu>,
"Ulli Horlacher" <framstag@rus.uni-stuttgart.de>
Subject: Re: [PATCH 00/10] cgroups: Task counter subsystem v8
Date: Mon, 5 Mar 2012 08:27:39 -0800 [thread overview]
Message-ID: <20120305162739.GP22536@google.com> (raw)
In-Reply-To: <20120305162652.GO22536@google.com>
On Mon, Mar 05, 2012 at 08:26:52AM -0800, Tejun Heo wrote:
> Hello, Frederic.
>
> On Mon, Mar 05, 2012 at 04:21:33AM +0100, Frederic Weisbecker wrote:
> > Time for me to try to wake up again this discussion.
> > Andrew, Tejun, Li, as you can see we don't lack the users
> > for this feature.
>
> Yes, I agree this can be a useful feature for certain use cases. I'm
> just mostly feeling reluctant about adding another utility type
> controller without clear direction on how to proceed from here on
> regarding multiple hierarchies (and I was on vacation :). That said,
> dealing with multiple hierarchies is a much longer term issue and
> we'll probably have to continue on our current path for the time
> being.
>
> We're already into -rc6, so unless someone objects I'll try to merge
> it after the coming merge window.
If I don't take action after the coming -rc1, please ping me. Thanks.
--
tejun
next prev parent reply other threads:[~2012-03-05 16:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 3:37 Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 01/10] cgroups: add res_counter_write_u64() API Frederic Weisbecker
2012-02-02 12:33 ` Kirill A. Shutemov
2012-02-02 13:56 ` Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 02/10] cgroups: new resource counter inheritance API Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 03/10] cgroups: ability to stop res charge propagation on bounded ancestor Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 04/10] cgroups: add res counter common ancestor searching Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 05/10] res_counter: allow charge failure pointer to be null Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 06/10] cgroups: pull up res counter charge failure interpretation to caller Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 07/10] cgroups: allow subsystems to cancel a fork Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 08/10] cgroups: Add a task counter subsystem Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 09/10] selftests: Enter each directories before executing selftests Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 10/10] selftests: Add a new task counter selftest Frederic Weisbecker
2012-02-01 16:31 ` [PATCH 00/10] cgroups: Task counter subsystem v8 Tejun Heo
2012-02-01 18:50 ` Frederic Weisbecker
2012-02-01 19:51 ` Andrew Morton
2012-02-02 14:50 ` Frederic Weisbecker
2012-02-16 15:31 ` Frederic Weisbecker
2012-03-01 22:53 ` Daniel Lezcano
2012-03-05 3:21 ` Frederic Weisbecker
2012-03-05 16:26 ` Tejun Heo
2012-03-05 16:27 ` Tejun Heo [this message]
2012-03-05 16:48 ` Frederic Weisbecker
2012-03-05 16:44 ` Rik van Riel
2013-04-01 18:43 ` Tim Hockin
2013-04-01 18:46 ` Tejun Heo
2013-04-01 20:09 ` Tim Hockin
2013-04-01 20:29 ` Tejun Heo
2013-04-01 21:02 ` Tim Hockin
2013-04-01 22:03 ` Tejun Heo
2013-04-01 22:20 ` Tim Hockin
2013-04-01 22:35 ` Tejun Heo
2013-04-01 22:57 ` Tim Hockin
2013-04-01 23:18 ` Tejun Heo
2013-04-02 0:07 ` Tim Hockin
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=20120305162739.GP22536@google.com \
--to=tj@kernel.org \
--cc=adityakali@google.com \
--cc=akpm@linux-foundation.org \
--cc=berrange@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=daniel.lezcano@free.fr \
--cc=dwalsh@redhat.com \
--cc=framstag@rus.uni-stuttgart.de \
--cc=fweisbec@gmail.com \
--cc=glommer@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mk@cm4all.com \
--cc=msb@chromium.org \
--cc=oleg@redhat.com \
--cc=paul@paulmenage.org \
--cc=thockin@hockin.org \
--cc=tompos@martos.bme.hu \
/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