[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6599ad830901201916o36e5e23bse440025618495ace@mail.gmail.com>
Date: Tue, 20 Jan 2009 19:16:42 -0800
From: Paul Menage <menage@...gle.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: matthltc@...ibm.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lizf@...fujitsu.com" <lizf@...fujitsu.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC][PATCH] NOOP cgroup subsystem
On Mon, Jan 19, 2009 at 7:07 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@...fujitsu.com> wrote:
> In my understanding, "sending signal" requires some protocol/order in userland.
>
> Assume that users has to send signal in following order
> Application A -> Application B -> Application C.....
> and may have problems sending signals in following order
> Application B -> Application A ->.....
In a case like that, a user would have to do their own signal sending
rather than letting the "signal" subsystem handle it. The signal
subsystem is more useful for doing things like sending less-refined
signals like SIGSTOP or SIGKILL to all tasks in a cgroup.
> multilply-mounted means its own hierachy can be created per mount point ?
Yes.
> If so, signal subsystem can be used instead of noop.
Supporting mounting a subsystem in multiple different hierarchies
would pretty much involve supporting mounting a hierarchy with no
subsystems (at least in the way I envisaged it), so you wouldn't need
any subsystem in that case if you were just trying to do grouping.
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists