From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: inux-next: Tree for Apr 27 (uml + mm/memcontrol.c)
Date: Fri, 27 Apr 2012 16:24:59 -0700 [thread overview]
Message-ID: <20120427162459.322d145a.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1204271611500.10429@chino.kir.corp.google.com>
On Fri, 27 Apr 2012 16:14:52 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> > Minor matter: that's non-responsive to my suggestion.
> >
>
> If it's moved to a new cgroup then we can just go back to the original
> point that I made as was trying to avoid: adding #ifdefs all over
> mm/memcontrol.c in a dozen or so places. A mm/hugetlbcg.c would only be
> built, natually, when we have "depends on HUGETLB_PAGE" and
> linux/hugetlb.h takes care of the rest (setting HUGE_MAX_HSTATE for archs
> that don't define it themselves, in other words only one hugepage size).
And if it isn't moved to a new cgroup then your
memcg-add-hugetlb-extension-fix.patch is suboptimal. Why is this so
hard?
next prev parent reply other threads:[~2012-04-27 23:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 6:11 inux-next: Tree for Apr 27 Stephen Rothwell
2012-04-27 15:47 ` inux-next: Tree for Apr 27 (uml + mm/memcontrol.c) Randy Dunlap
2012-04-27 18:44 ` David Rientjes
2012-04-27 20:23 ` Andrew Morton
2012-04-27 21:27 ` David Rientjes
2012-04-27 21:36 ` Andrew Morton
2012-04-27 23:14 ` David Rientjes
2012-04-27 23:24 ` Andrew Morton [this message]
2012-04-27 23:52 ` David Rientjes
2012-04-28 18:01 ` Aneesh Kumar K.V
2012-05-03 9:13 ` David Rientjes
2012-05-03 10:30 ` Hiroyuki Kamezawa
2012-05-03 20:56 ` David Rientjes
2012-05-03 21:57 ` David Rientjes
2012-05-03 23:21 ` Hiroyuki Kamezawa
2012-05-03 23:33 ` Hiroyuki Kamezawa
2012-05-04 18:29 ` Aneesh Kumar K.V
2012-05-03 23:17 ` Hiroyuki Kamezawa
2012-05-04 17:24 ` Tejun Heo
2012-05-07 14:01 ` Michal Hocko
2012-05-07 17:08 ` Tejun Heo
2012-05-08 10:48 ` Michal Hocko
2012-05-03 13:54 ` Aneesh Kumar K.V
2012-05-03 20:39 ` David Rientjes
2012-04-28 0:45 ` Randy Dunlap
2012-04-27 16:56 ` inux-next: Tree for Apr 27 (infiniband/hw/ocrdma) Randy Dunlap
2012-04-27 23:54 ` Roland Dreier
2012-05-02 22:51 ` [PATCH] RDMA/ocrdma: Fix build with IPV6=n Roland Dreier
2012-05-03 0:29 ` Randy Dunlap
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=20120427162459.322d145a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox