From: Ian Kumlien <pomac@vapor.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [BUG?] numa required on x86_64?
Date: Sat, 25 Jun 2011 02:06:32 +0200 [thread overview]
Message-ID: <1308960392.25830.11.camel@pi> (raw)
In-Reply-To: <20110624152310.10803ffa.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]
On fre, 2011-06-24 at 15:23 -0700, Randy Dunlap wrote:
> On Sat, 25 Jun 2011 00:00:58 +0200 Ian Kumlien wrote:
>
> > Hi all,
> >
> > Just found this when wanting to play with development kernels again.
> > Since there is no -gitXX snapshots anymore, I cloned the git =)...
> >
> > But, it failed to build properly with my config:
> >
> > mm/page_cgroup.c line 308: node_start_pfn and node_end_pfn is only
> > defined under NUMA on x86_64.
> >
> > The commit that changed the use of this was introduced recently while
> > the mmzone_64.h hasn't been changed since april.
>
> You should have cc-ed the commit Author (I did so).
Sorry, tired and i was upgrading systems at work when i found this =)
> > commit 37573e8c718277103f61f03741bdc5606d31b07e
> > Author: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > Date: Wed Jun 15 15:08:42 2011 -0700
> >
> > memcg: fix init_page_cgroup nid with sparsemem
> >
> > Commit 21a3c9646873 ("memcg: allocate memory cgroup structures in local
> > nodes") makes page_cgroup allocation as NUMA aware. But that caused a
> > problem https://bugzilla.kernel.org/show_bug.cgi?id=36192.
> >
> > The problem was getting a NID from invalid struct pages, which was not
> > initialized because it was out-of-node, out of [node_start_pfn,
> > node_end_pfn)
> >
> > Now, with sparsemem, page_cgroup_init scans pfn from 0 to max_pfn. But
> > this may scan a pfn which is not on any node and can access memmap which
> > is not initialized.
> >
> > This makes page_cgroup_init() for SPARSEMEM node aware and remove a code
> > to get nid from page->flags. (Then, we'll use valid NID always.)
> >
> > [akpm@linux-foundation.org: try to fix up comments]
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> A patch for this has been posted at least 2 times.
> It's here: http://marc.info/?l=linux-mm&m=130827204306775&w=2
>
> Andrew, please merge this (^that^) patch.
Damn, i haven't been following LKML that closely recently =/
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
--
Ian Kumlien -- http://demius.net || http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-06-25 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308952859.25830.8.camel@pi>
2011-06-24 22:23 ` [BUG?] numa required on x86_64? Randy Dunlap
2011-06-25 0:06 ` Ian Kumlien [this message]
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=1308960392.25830.11.camel@pi \
--to=pomac@vapor.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=randy.dunlap@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).