From: Randolph Chung <tausq@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Problem with no mem_map arg to init functions change?
Date: Thu, 02 Sep 2004 17:43:19 +0000 [thread overview]
Message-ID: <20040902174319.GN19210@tausq.org> (raw)
In-Reply-To: <20040902053659.GG21873@cse.unsw.EDU.AU>
> Are you creating the whole memmap and then freeing up the holes? IIRC that's
> what's done for x86 NUMA boxes, but that won't work if the inital memmap is
> too big to fit in memory in the first place.
this is what we do:
for (i = 0; i < npmem_ranges; i++) {
unsigned long start_pfn;
unsigned long npages;
start_pfn = pmem_ranges[i].start_pfn;
npages = pmem_ranges[i].pages;
bootmap_size = init_bootmem_node(NODE_DATA(i),
bootmap_pfn,
start_pfn,
(start_pfn + npages) );
free_bootmem_node(NODE_DATA(i),
(start_pfn << PAGE_SHIFT),
(npages << PAGE_SHIFT) );
bootmap_pfn += (bootmap_size + PAGE_SIZE - 1) >> PAGE_SHIFT;
if ((start_pfn + npages) > max_pfn)
max_pfn = start_pfn + npages;
}
we don't do anything explicit with the holes when DISCONTIGMEM is
enabled. when it's not enabled we are able to work with small holes by
using the technique you mentioned above.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-09-02 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 5:36 Problem with no mem_map arg to init functions change? Ian Wienand
2004-09-02 6:10 ` William Lee Irwin III
2004-09-02 6:21 ` Ian Wienand
2004-09-02 15:05 ` Matthew Wilcox
2004-09-02 15:31 ` Jesse Barnes
2004-09-02 15:33 ` Jesse Barnes
2004-09-02 16:10 ` Randolph Chung
2004-09-02 16:16 ` Jesse Barnes
2004-09-02 17:43 ` Randolph Chung [this message]
2004-09-02 18:42 ` William Lee Irwin III
2004-09-03 2:19 ` Ian Wienand
2004-09-03 2:31 ` William Lee Irwin III
2004-09-03 6:09 ` Luck, Tony
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=20040902174319.GN19210@tausq.org \
--to=tausq@debian.org \
--cc=linux-ia64@vger.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