Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758786AbYGJQwU (ORCPT ); Thu, 10 Jul 2008 12:52:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753088AbYGJQwM (ORCPT ); Thu, 10 Jul 2008 12:52:12 -0400 Received: from smtp-out.google.com ([216.239.33.17]:33672 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750881AbYGJQwL (ORCPT ); Thu, 10 Jul 2008 12:52:11 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references; b=cVpiVUOW+337ZCvsk3Hw2PMdfdMvUvgcEdaQ9ZBjceNIgB5gRHWOGG7NqUrgmH6kj WvBloAwHAiEmv3GG9QM6Q== Message-ID: <6599ad830807100951w53c54f0cl50bddb4286bc696e@mail.gmail.com> Date: Thu, 10 Jul 2008 09:51:52 -0700 From: "Paul Menage" To: "Vivek Goyal" Subject: Re: [RFC] How to handle the rules engine for cgroups Cc: "KAMEZAWA Hiroyuki" , "linux kernel mailing list" , "Libcg Devel Mailing List" , "Balbir Singh" , "Dhaval Giani" , "Peter Zijlstra" , "Kazunaga Ikeno" , "Morton Andrew Morton" , "Thomas Graf" , "Rik Van Riel" In-Reply-To: <20080710143018.GC3782@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080701191126.GA17376@redhat.com> <20080703101957.b3856904.kamezawa.hiroyu@jp.fujitsu.com> <20080703155446.GB9275@redhat.com> <6599ad830807100223m2453963cwcfbe6eb1ad54d517@mail.gmail.com> <20080710143018.GC3782@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1049 Lines: 25 On Thu, Jul 10, 2008 at 7:30 AM, Vivek Goyal wrote: > > Well, that would mean first wrappers need to be created around all the > applications which needs to be controlled. Then wrapper needs to > synchronize with the classification daemon I was suggesting that you wouldn't need a classification daemon in this case. The logic of which cgroup to enter would be in the script/command invoked by the wrapper. >> - grid jobs, which are moved into the appropriate cgroup (actually, >> currently cpuset) by the grid daemon when it starts the job > > So grid daemon probably first forks off, determines the right cpuset > move the job there and then do exec? Pretty much, yes. Most jobs have their own cpuset that's created for them dynamically when the job starts on the machine. Paul -- 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/