From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: naren.mehra@gmail.com
Cc: Minchan Kim <minchan.kim@gmail.com>, linux-mm@kvack.org
Subject: Re: Need some help in understanding sparsemem.
Date: Fri, 9 Jul 2010 16:49:32 +0900 [thread overview]
Message-ID: <20100709164932.5e5fd045.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <AANLkTil7X11whzqzsTudHQNCuFJKprTsStHVQNRgbYZD@mail.gmail.com>
On Fri, 9 Jul 2010 12:35:17 +0530
naren.mehra@gmail.com wrote:
> Thanks to you guys, I am now getting a grip on the sparsemem code.
> While going through the code, I came across several instances of the following:
> #ifndef CONFIG_NEED_MULTIPLE_NODES
> .
> <some code>
> .
> #endif
>
> Now, it seems like this configuration option is used in case there are
> multiple nodes in a system.
> But its linked/depends on NUMA/discontigmem.
>
> It could be possible that we have multiple nodes in a UMA system.
> How can sparsemem handle such cases ??
>
sparsemem can be used both in UMA/NUMA case. IOW, sparsemem is for handling
memmap(array of struct page) for flexible memory layout, and not for NUMA.
Then, NUMA/MULTIPLENODE and SPARSEMEM has no relationship, basically.
"nid" is recorded just for detecting the nearest node for allocating mem_map.
(And some 32bit arch recoreds some information of 'nid'.)
So, you shouldn't be suffer from an illusion of sparsemem when you think about
NUMA/MULTIPLENODE. please visit free_area_init_nodes(), and add_active_range(),
remove_actitve_range(). They are for MULTIPLENODES.
Thanks,
-Kame
--
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>
prev parent reply other threads:[~2010-07-09 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 5:11 naren.mehra
2010-07-06 6:07 ` KAMEZAWA Hiroyuki
2010-07-06 7:06 ` Minchan Kim
2010-07-06 7:36 ` Minchan Kim
2010-07-06 10:48 ` naren.mehra
2010-07-07 3:49 ` Minchan Kim
2010-07-09 7:05 ` naren.mehra
2010-07-09 7:49 ` KAMEZAWA Hiroyuki [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=20100709164932.5e5fd045.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=naren.mehra@gmail.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