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 16:10:02 +0000 [thread overview]
Message-ID: <20040902161002.GM19210@tausq.org> (raw)
In-Reply-To: <20040902053659.GG21873@cse.unsw.EDU.AU>
> > If DISCONTIGMEM now works properly, I think VIRTUAL_MEM_MAP can disappear.
>
> Except that the former uses the latter, and that won't change without a bit
> more work. Even then, CONFIG_NUMA and CONFIG_DISCONTIGMEM are somewhat
> intertwined at this point, so using the discontig code to deal with a zx1
> memory layout isn't a good match.
fwiw we recently implemented CONFIG_DISCONTIGMEM for parisc-linux to better
support N-class (and pa8800, which uses zx1). You are right that CONFIG_NUMA
and CONFIG_DISCONTIGMEM are a bit intertwined, but it can be made to work
:)
For reference we are targetting these three memory layouts:
* Astro: 0-3.75, 67.75-68, 4-64
* zx1: 0-1, 257-260, 4-256
* Stretch (N-class): 0-2, 4-32, 34-xxx
Astro and Stretch have been verified (up to 32GB, so 3 zones), zx1
verification is still pending, but i don't see why it wouldn't work (famous
last words? :)
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-09-02 16:10 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 [this message]
2004-09-02 16:16 ` Jesse Barnes
2004-09-02 17:43 ` Randolph Chung
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=20040902161002.GM19210@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