Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758840AbYGJPtn (ORCPT ); Thu, 10 Jul 2008 11:49:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751080AbYGJPte (ORCPT ); Thu, 10 Jul 2008 11:49:34 -0400 Received: from mx1.redhat.com ([66.187.233.31]:59167 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751365AbYGJPtd (ORCPT ); Thu, 10 Jul 2008 11:49:33 -0400 Date: Thu, 10 Jul 2008 11:40:35 -0400 From: Vivek Goyal To: Rik van Riel Cc: Paul Menage , KAMEZAWA Hiroyuki , linux kernel mailing list , Libcg Devel Mailing List , Balbir Singh , Dhaval Giani , Peter Zijlstra , Kazunaga Ikeno , Morton Andrew Morton , Thomas Graf , Ulrich Drepper Subject: Re: [RFC] How to handle the rules engine for cgroups Message-ID: <20080710154035.GA12043@redhat.com> References: <20080701191126.GA17376@redhat.com> <20080703101957.b3856904.kamezawa.hiroyu@jp.fujitsu.com> <20080703155446.GB9275@redhat.com> <6599ad830807100223m2453963cwcfbe6eb1ad54d517@mail.gmail.com> <20080710104852.797fe79c@cuia.bos.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080710104852.797fe79c@cuia.bos.redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1475 Lines: 40 On Thu, Jul 10, 2008 at 10:48:52AM -0400, Rik van Riel wrote: > On Thu, 10 Jul 2008 02:23:52 -0700 > "Paul Menage" wrote: > > > I don't see the rule-based approach being all that useful for our needs. > > Agreed, there really is no need for a rule-based approach in kernel space. > > There are basically three different cases: > > 1) daemons get started up in their own process groups, this can > be handled by the initscripts > > 2) user sessions (ssh, etc) start in their own process groups, > this can be handled by PAM > > 3) users fork processes that should go into special process > groups - this could be handled by having a small ruleset > in userspace handle things, right before calling exec(), That means application launcher (ex, shell) is aware of the right cgroup targeted application should go in and then move forked pid to right cgroup and call exec? Or you had something else in mind? > it can even be hidden from the application by hooking into > the exec() call > This means hooking into libc. So libc will parse rules file, determine the right cgroup, place application there and then call exec? CCing, Ulrich also in case he has some thoughts. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/