From: Pekka Enberg <penberg@cs.helsinki.fi>
To: balbir@linux.vnet.ibm.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, hannes@cmpxchg.org,
torvalds@linux-foundation.org, yinghai@kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [BUGFIX][PATCH] memcg: fix page_cgroup fatal error in FLATMEM v2
Date: Mon, 15 Jun 2009 14:10:45 +0300 [thread overview]
Message-ID: <1245064245.23207.28.camel@penberg-laptop> (raw)
In-Reply-To: <4A3270FE.4090602@linux.vnet.ibm.com>
On Fri, 2009-06-12 at 20:45 +0530, Balbir Singh wrote:
> > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> >
> > Now, SLAB is configured in very early stage and it can be used in
> > init routine now.
> >
> > But replacing alloc_bootmem() in FLAT/DISCONTIGMEM's page_cgroup()
> > initialization breaks the allocation, now.
> > (Works well in SPARSEMEM case...it supports MEMORY_HOTPLUG and
> > size of page_cgroup is in reasonable size (< 1 << MAX_ORDER.)
> >
> > This patch revive FLATMEM+memory cgroup by using alloc_bootmem.
> >
> > In future,
> > We stop to support FLATMEM (if no users) or rewrite codes for flatmem
> > completely.But this will adds more messy codes and overheads.
> >
> > Changelog: v1->v2
> > - fixed typos.
> >
> > Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
> > Tested-by: Li Zefan <lizf@cn.fujitsu.com>
> > Reported-by: Li Zefan <lizf@cn.fujitsu.com>
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> I see you've responded already, Thanks!
>
> The diff is a bit confusing, was Pekka's patch already integrated, in my version
> of mmotm, I don't see the alloc_pages_node() change in my source base.
Yes, my patch hit mainline on Thursday or so and this patch is now in as well.
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-15 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0906110820170.2258@melkki.cs.Helsinki.FI>
2009-06-12 2:50 ` boot panic with memcg enabled (Was [PATCH 3/4] memcg: don't use bootmem allocator in setup code) Li Zefan
2009-06-12 2:55 ` KAMEZAWA Hiroyuki
2009-06-12 3:44 ` KAMEZAWA Hiroyuki
2009-06-12 4:01 ` Li Zefan
2009-06-12 5:34 ` [BUGFIX][PATCH] memcg: fix page_cgroup fatal error in FLATMEM (Was Re: boot panic with memcg enabled KAMEZAWA Hiroyuki
2009-06-12 6:01 ` Li Zefan
2009-06-12 6:21 ` Pekka Enberg
2009-06-12 6:29 ` [BUGFIX][PATCH] memcg: fix page_cgroup fatal error in FLATMEM v2 KAMEZAWA Hiroyuki
2009-06-12 15:15 ` Balbir Singh
2009-06-15 11:10 ` Pekka Enberg [this message]
2009-06-12 15:02 ` boot panic with memcg enabled (Was [PATCH 3/4] memcg: don't use bootmem allocator in setup code) Balbir Singh
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=1245064245.23207.28.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=balbir@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox