From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Problem with no mem_map arg to init functions change?
Date: Thu, 02 Sep 2004 15:33:41 +0000 [thread overview]
Message-ID: <200409020833.41165.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040902053659.GG21873@cse.unsw.EDU.AU>
On Thursday, September 2, 2004 8:05 am, Matthew Wilcox wrote:
> On Wed, Sep 01, 2004 at 11:10:30PM -0700, William Lee Irwin III wrote:
> > You don't thave CONFIG_DISCONTIGMEM set? Why are you bothering with
> > virtual mem_map if not? If the core helpers are insufficiently
> > lightweight in the CONFIG_DISCONTIGMEM=n case we are very well going
> > to have whatever sanction we need to repair it, as this is the common
> > case among end users of the most predominant hardware and architectures.
>
> Ah, basic lack of understanding of what VIRTUAL_MEM_MAP is used for
> and why it exists. It should be exclusive with DISCONTIGMEM as they
> both solve the same problem, but in wildly different ways.
Well, on ia64 it's used *by* DISCONTIGMEM to deal with nodes that have sparse
memory layouts.
> 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.
Jesse
next prev parent reply other threads:[~2004-09-02 15:33 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 [this message]
2004-09-02 16:10 ` Randolph Chung
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=200409020833.41165.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--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