DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to:
	cc:content-type:content-transfer-encoding:x-system-of-record;
	b=BVcQdqGCn3OSmZm+N6Qm/HsNIkjkUeBSDIihZ/SpgrOtzxxkMNh1dnG/byVDJ4Cdv
	jfVoSsTIcJtWXSlHjobmg==
MIME-Version: 1.0
In-Reply-To: <20090702114829.df04c885.kamezawa.hiroyu@jp.fujitsu.com>
References: <20090702020624.14469.47066.stgit@menage.mtv.corp.google.com>
	 <20090702021133.14469.35140.stgit@menage.mtv.corp.google.com>
	 <20090702114829.df04c885.kamezawa.hiroyu@jp.fujitsu.com>
Date: Wed, 1 Jul 2009 19:56:28 -0700
Message-ID: <6599ad830907011956i33769d5ek5401e93553d75c59@mail.gmail.com>
Subject: Re: [PATCH 8/9] [RFC] Example multi-bindable subsystem: a per-cgroup 
	notes field
From: Paul Menage <menage@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: lizf@cn.fujitsu.com, balbir@linux.vnet.ibm.com,
       linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
       containers@lists.linux-foundation.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1018
Lines: 24

On Wed, Jul 1, 2009 at 7:48 PM, KAMEZAWA
Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> Hmm, do we need to this "info" file as subsys ? How about making this as
> default file set ? (if there are users.)
>

That would certainly be possible, and would be an alternative to
having multi-bindable subsystem support.

The advantage of adding multi-bindable subsystems is that you can
avoid bloating the core cgroups code, by putting individual small
cgroups features in their own code modules, and you get to decide at
mount time which features are actually mounted; if they were part of
the core cgroups files, then there would either need to be special
mount options for each separate feature, or else no way to pick which
features were mounted on each hierarchy.

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/