linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: naren.mehra@gmail.com
Cc: linux-mm@kvack.org
Subject: Re: Need some help in understanding sparsemem.
Date: Tue, 6 Jul 2010 16:36:37 +0900	[thread overview]
Message-ID: <AANLkTik9TlLYbG4GE6TV1wF7SOXz7v7gQ1BR531HGyNx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil6go0otCsBkG_detjptXX_i_mNkkCMawLVIz82@mail.gmail.com>

On Tue, Jul 6, 2010 at 2:11 PM,  <naren.mehra@gmail.com> wrote:
> Hi,
>
> I am trying to understand the sparsemem implementation in linux for
> NUMA/multiple node systems.
>
> From the available documentation and the sparsemem patches, I am able
> to make out that sparsemem divides memory into different sections and
> if the whole section contains a hole then its marked as invalid
> section and if some pages in a section form a hole then those pages
> are marked reserved. My issue is that this classification, I am not
> able to map it to the code.
>
> e.g. from arch specific code, we call memory_present()  to prepare a
> list of sections in a particular node. but unable to find where
> exactly some sections are marked invalid because they contain a hole.

On ARM's sparsememory,

static void arm_memory_present(struct meminfo *mi)
{
        int i;
        for_each_bank(i, mi) {
                struct membank *bank = &mi->bank[i];
                memory_present(0, bank_pfn_start(bank), bank_pfn_end(bank));
        }
}

It just mark _bank_ which has memory with SECTION_MARKED_PRESENT.
Otherwise, Hole.

>
> Can somebody tell me where in the code are we identifying sections as
> invalid and where we are marking pages as reserved.

Do you mean memmap_init_zone?


-- 
Kind regards,
Minchan Kim

--
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>

  parent reply	other threads:[~2010-07-06  7:36 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 [this message]
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

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=AANLkTik9TlLYbG4GE6TV1wF7SOXz7v7gQ1BR531HGyNx@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=linux-mm@kvack.org \
    --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