Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755930AbYCQB56 (ORCPT ); Sun, 16 Mar 2008 21:57:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753298AbYCQB5t (ORCPT ); Sun, 16 Mar 2008 21:57:49 -0400 Received: from smtp-out.google.com ([216.239.33.17]:14452 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752379AbYCQB5s (ORCPT ); Sun, 16 Mar 2008 21:57:48 -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=EmhBFsJ6s84Rzy0f2vWzXDHUpwdaiydg7LhOGqXk0sOECRiLp3pSzKJOr4xFbAiIX 76xdWJt58HAL2CSHrTzpA== Message-ID: <6599ad830803161857r6d01f962vfd0f570e6124ab24@mail.gmail.com> Date: Mon, 17 Mar 2008 09:57:37 +0800 From: "Paul Menage" To: "Li Zefan" Subject: Re: [RFC][0/3] Virtual address space control for cgroups Cc: "Balbir Singh" , linux-mm@kvack.org, "Hugh Dickins" , "Sudhir Kumar" , "YAMAMOTO Takashi" , linux-kernel@vger.kernel.org, taka@valinux.co.jp, "David Rientjes" , "Pavel Emelianov" , "Andrew Morton" , "KAMEZAWA Hiroyuki" In-Reply-To: <47DDCDA7.4020108@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080316172942.8812.56051.sendpatchset@localhost.localdomain> <6599ad830803161626q1fcf261bta52933bb5e7a6bdd@mail.gmail.com> <47DDCDA7.4020108@cn.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 890 Lines: 20 On Mon, Mar 17, 2008 at 9:47 AM, Li Zefan wrote: > > It will be code duplication to make it a new subsystem, Would it? Other than the basic cgroup boilerplate, the only real duplication that I could see would be that there'd need to be an additional per-mm pointer back to the cgroup. (Which could be avoided if we added a single per-mm pointer back to the "owning" task, which would generally be the mm's thread group leader, so that you could go quickly from an mm to a set of cgroup subsystems). And the advantage would that you'd be able to more easily pick/choose which bits of control you use (and pay for). 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/