From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: serge@hallyn.com, Andrew Morton <akpm@linux-foundation.org>,
containers@lists.osdl.org, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, xemul@openvz.org, pj@sgi.com
Subject: Re: [RFC] Prefixing cgroup generic control filenames with "cgroup."
Date: Mon, 03 Mar 2008 15:29:29 +0530 [thread overview]
Message-ID: <47CBCC01.6080504@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830803030038p2d81883bu895260a96fedaec6@mail.gmail.com>
Paul Menage wrote:
> On Thu, Feb 28, 2008 at 2:06 PM, Paul Menage <menage@google.com> wrote:
>> On Thu, Feb 28, 2008 at 1:33 PM, <serge@hallyn.com> wrote:
>> >
>> > You said the set of files belong to cgroup itself is likely to increase
>> > - do you have some candidates in mind?
>>
>> Nothing concrete right now. One example that I already proposed was
>> the "cgroup.api" file but that's shelved for now, until such time as I
>> actually propose the binary API that it was intended to help support.
>>
>
> One likely new file that people agreed a while ago could be useful
> would be a "procs" file, similar to "tasks", but acting (and
> reporting) on thread groups rather than individual tasks.
>
> Paul
Yes, I remember this. This feature would be extremely useful.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-03-03 10:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 21:14 [RFC] Prefixing cgroup generic control filenames with "cgroup." Paul Menage
2008-02-28 21:21 ` Andrew Morton
2008-02-28 21:28 ` Paul Menage
2008-02-28 21:33 ` serge
2008-02-28 22:06 ` Paul Menage
2008-03-03 8:38 ` Paul Menage
2008-03-03 9:59 ` Balbir Singh [this message]
2008-02-28 21:40 ` Andrew Morton
2008-02-28 22:06 ` Paul Menage
2008-02-28 22:21 ` Andrew Morton
2008-02-28 22:26 ` Paul Menage
2008-02-29 5:59 ` [RFC] [PATCH] " Paul Menage
2008-02-29 6:20 ` Paul Jackson
2008-02-29 9:34 ` Paul Menage
2008-02-29 15:30 ` Paul Jackson
2008-02-29 17:59 ` Paul Menage
2008-02-29 19:20 ` Paul Jackson
2008-02-28 21:28 ` [RFC] " serge
2008-02-28 23:36 ` Paul Jackson
2008-02-29 1:03 ` Paul Menage
2008-02-29 1:22 ` Paul Jackson
2008-02-29 11:38 ` Xpl++
2008-03-03 7:23 ` Li Zefan
2008-03-03 9:11 ` Paul Menage
2008-03-05 1:24 ` Paul Jackson
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=47CBCC01.6080504@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=serge@hallyn.com \
--cc=xemul@openvz.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