From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Blum <bblum@google.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, serue@us.ibm.com,
lizf@cn.fujitsu.com, menage@google.com, bblum@google.com
Subject: Re: [PATCH v3 0/7] CGroups: cgroup memberlist enhancement+fix
Date: Tue, 18 Aug 2009 14:33:58 -0700 [thread overview]
Message-ID: <20090818143358.9cc9aff3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090811004737.21950.29188.stgit@hastromil.mtv.corp.google.com>
On Mon, 10 Aug 2009 17:57:30 -0700
Ben Blum <bblum@google.com> wrote:
> The following series adds a "cgroup.procs" file to each cgroup that reports
> unique tgids rather than pids, which can also be written to for moving all
> threads in a threadgroup at once.
Well that didn't get much of a response, did it.
Any acks, nacks or quacks from the cgroups guys, please?
prev parent reply other threads:[~2009-08-18 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 0:57 [PATCH v3 0/7] CGroups: cgroup memberlist enhancement+fix Ben Blum
2009-08-11 0:57 ` [PATCH 1/7] Adds a read-only "procs" file similar to "tasks" that shows only unique tgids Ben Blum
2009-08-11 0:57 ` [PATCH 2/7] Ensures correct concurrent opening/reading of pidlists across pid namespaces Ben Blum
2009-08-11 0:57 ` [PATCH 3/7] Quick vmalloc vs kmalloc fix to the case where array size is too large Ben Blum
2009-08-11 0:57 ` [PATCH 4/7] Changes css_set freeing mechanism to be under RCU Ben Blum
2009-08-11 0:57 ` [PATCH 5/7] Lets ss->can_attach and ss->attach do whole threadgroups at a time Ben Blum
2009-08-11 0:58 ` [PATCH 6/7] Adds functionality to read/write lock CLONE_THREAD fork()ing per-threadgroup Ben Blum
2009-08-11 0:58 ` [PATCH 7/7] Makes procs file writable to move all threads by tgid at once Ben Blum
2009-08-18 21:33 ` Andrew Morton [this message]
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=20090818143358.9cc9aff3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bblum@google.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=serue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox