[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0804211301500.20183@blonde.site>
Date: Mon, 21 Apr 2008 13:13:38 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: Andi Kleen <andi@...stfloor.org>
cc: Balbir Singh <balbir@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
menage@...gle.com, xemul@...nvz.org, shiwh@...fujitsu.com,
mel@....ul.ie, linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.26 (memcgroup)
On Mon, 21 Apr 2008, Andi Kleen wrote:
> Hugh Dickins wrote:
> > On Mon, 21 Apr 2008, Balbir Singh wrote:
> > I've added Andi to the Cc's, I don't want to sneak away something
> > he's expecting there. If 2.6.25 had gone out with a convention that
> > controller infrastructure gets compiled in, but has then to be enabled
> > at boottime or runtime, okay;
>
> That is what I have been expecting yes.
>
> If later the slow down is fixed it can be also enabled by default too.
It is disabled by default, in the config; and Paul/Balbir already
provided the cgroup_disable=memory bootoption to override that.
Is it wise to add an additional hurdle now that 2.6.25 has gone out?
Is it wise to switch it around in future? Seems a source of confusion
to me (I already wasted time testing the same things twice in -mm
because of this).
I guess Andrew needs to make an executive decision!
Whichever way round, we ought to clarify the config helptext.
Hugh
--
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