From: Paul Menage <menage@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] NOOP cgroup subsystem
Date: Thu, 8 Jan 2009 22:26:46 -0800 [thread overview]
Message-ID: <6599ad830901082226h6d47053cp801dafb67b6e2bc9@mail.gmail.com> (raw)
In-Reply-To: <20090109143226.b79d21b4.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Jan 8, 2009 at 9:32 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> Motivation: Simply classify Applications by cgroup
> When using cgroup for classifying applications, some kind of "control" or
> "account" subsys must be used. For flexible use of cgroup's nature of
> classifying applications, NOOP is useful. It can be used regardless of
> resource accounting unit or name spaces or some controls.
> IOW, NOOP cgroup allows users to tie PIDs with some nickname.
I agree that the idea is useful. But to me it seems to a bit
artificial that you still have to mount some kind of subsystem purely
to get the grouping, and that you can only have one such grouping.
I think I'd prefer the ability to mount a cgroups hierarchy without
*any* subsystems (maybe with "-o none"?) which would give you a
similar effect, but without you needing to know about a special no-op
subsystem, and would allow you to have multiple "no-op" groupings.
Paul
next prev parent reply other threads:[~2009-01-09 6:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 5:32 KAMEZAWA Hiroyuki
2009-01-09 6:14 ` Li Zefan
2009-01-09 6:24 ` KAMEZAWA Hiroyuki
2009-01-09 6:27 ` Paul Menage
2009-01-09 6:26 ` Paul Menage [this message]
2009-01-09 6:29 ` Li Zefan
2009-01-09 6:37 ` Paul Menage
2009-01-09 6:44 ` Li Zefan
2009-01-09 7:22 ` KAMEZAWA Hiroyuki
2009-01-09 21:15 ` Paul Menage
2009-01-09 6:32 ` KAMEZAWA Hiroyuki
2009-01-16 2:20 ` Matthew Helsley
2009-01-16 2:45 ` KAMEZAWA Hiroyuki
2009-01-16 3:02 ` KAMEZAWA Hiroyuki
2009-01-20 1:52 ` Paul Menage
2009-01-20 3:07 ` KAMEZAWA Hiroyuki
2009-01-21 2:36 ` Matt Helsley
2009-01-21 3:16 ` Paul Menage
2009-01-09 6:34 ` Daisuke Nishimura
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=6599ad830901082226h6d47053cp801dafb67b6e2bc9@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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
all inboxes | Powered by JetHome®