[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1156539168.3007.264.camel@localhost.localdomain>
Date: Fri, 25 Aug 2006 21:52:47 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: sekharan@...ibm.com
Cc: Kirill Korotaev <dev@...ru>, Rik van Riel <riel@...hat.com>,
ckrm-tech@...ts.sourceforge.net, Andi Kleen <ak@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Andrey Savochkin <saw@...ru>, rohitseth@...gle.com,
hugh@...itas.com, Ingo Molnar <mingo@...e.hu>, devel@...nvz.org,
Pavel Emelianov <xemul@...nvz.org>
Subject: Re: [ckrm-tech] [RFC][PATCH] UBC: user resource beancounters
Ar Gwe, 2006-08-25 am 11:47 -0700, ysgrifennodd Chandra Seetharaman:
> I think my original point is getting lost in the discussion, which is,
> there should be way (for the sysadmin) to get a list of tasks belonging
> to a resource group (in a non-container environment).
Ok that much is easy to deal with. You print the luid in /proc.
> - ability for the sysadmin to move a task to a resource group.
So you want a setpluid(pid, luid) ? Trivial to add although you might
want to refuse it in many secure environments but thats an SELinux rule
again.
> - assignment of task to a resource group should be transparent to the
> app.
In those cases its akin to and matches security domain transitions which
says to me SELinux (or AppArmour) should do it.
> - a resource group could exist with no tasks associated.
Bean counters can exist with no tasks, and the CKRM people have been
corrected repeatedly on this point.
-
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