From: Paul Menage <menage@google.com>
To: matthltc@us.ibm.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"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>,
Containers <containers@lists.linux-foundation.org>
Subject: Re: [RFC][PATCH] NOOP cgroup subsystem
Date: Mon, 19 Jan 2009 17:52:36 -0800 [thread overview]
Message-ID: <6599ad830901191752o53926bdbve593301aeff7330f@mail.gmail.com> (raw)
In-Reply-To: <1232072445.7955.40.camel@localhost>
On Thu, Jan 15, 2009 at 6:20 PM, Matthew Helsley <matthltc@us.ibm.com> wrote:
>
> My feeling is this should be a signal subsystem rather than a NOOP
> subsystem. Then, if users want the grouping for something besides
> signaling, it doesn't matter if they don't issue any signals via the
> signal.send file. Also, I think Paul's suggestion would be just as
> useful for a signal subsystem.
The signal subsystem is similar to the "no-op" subsystem in that
neither of them actually need any state - in principle, it could be
useful to attach a signal subsys to multiple mounted hierarchies, to
provide signal semantics for each of them.
Would it make sense to allow a class of subsystem that explicitly has
no state (or at least, has no state that has a global meaning on the
machine), so that it can be multiply-mounted?
Paul
next prev parent reply other threads:[~2009-01-20 1:52 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
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 [this message]
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=6599ad830901191752o53926bdbve593301aeff7330f@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthltc@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
all inboxes | Powered by JetHome®