From: Andi Kleen <andi@firstfloor.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
menage@google.com, xemul@openvz.org, shiwh@cn.fujitsu.com,
mel@csn.ul.ie, linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans for 2.6.26 (memcgroup)
Date: Mon, 21 Apr 2008 13:41:00 +0200 [thread overview]
Message-ID: <480C7D4C.1070502@firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804211158001.10521@blonde.site>
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.
-Andi
next prev parent reply other threads:[~2008-04-21 11:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 14:20 -mm merge plans for 2.6.26 Andrew Morton
2008-04-20 15:51 ` Jiri Slaby
2008-04-20 23:51 ` -mm merge plans for 2.6.26 (memcgroup) Hugh Dickins
2008-04-21 0:30 ` KAMEZAWA Hiroyuki
2008-04-21 6:24 ` Andrew Morton
[not found] ` <480C347C.6060702@linux.vnet.ibm.com>
2008-04-21 6:47 ` Balbir Singh
2008-04-21 9:42 ` Peter Zijlstra
2008-04-21 10:21 ` Balbir Singh
2008-04-21 10:40 ` KAMEZAWA Hiroyuki
2008-04-21 15:48 ` Paul Menage
2008-04-21 11:22 ` Hugh Dickins
2008-04-21 11:41 ` Andi Kleen [this message]
2008-04-21 12:13 ` Hugh Dickins
2008-04-21 13:31 ` kamezawa.hiroyu
2008-04-21 11:41 ` Balbir Singh
2008-05-17 0:03 ` -mm merge plans for 2.6.26 Randy Dunlap
2008-05-17 0:28 ` Andrew Morton
2008-05-17 2:07 ` Randy Dunlap
2008-05-17 4:30 ` Randy Dunlap
2008-05-19 20:26 ` Randy Dunlap
2008-05-19 20:38 ` Andrew Morton
2008-05-19 20:44 ` Sam Ravnborg
2008-05-23 8:05 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480C7D4C.1070502@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=menage@google.com \
--cc=shiwh@cn.fujitsu.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.