public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] discontig patch (work in progress)
Date: Wed, 24 Sep 2003 16:54:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106442331327396@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106436165231302@msgid-missing>

On Wed, Sep 24, 2003 at 07:51:39AM -0700, Jesse Barnes wrote:
> > The #if defined(VIRTUAL_MEM_MAP) || !defined(DISCONTIGMEM) in generic
> > code have to go away.  All this mem_map/contig_page_data/etc crap
> > has should probably go away some day, but for now let's not make it
> > even messier.
> 
> Sure, I'm all for them going away, any suggestions on how to get there?

Always use the node-local mem_map, in the !DISCONTIG case we just
have only one of them.  But as said above this is in scope for this
work (or 2.6 at all).

> > Also in the discontig + vmem_map case you don't want them - always use
> > the per-node mem_maps even if it's just to avoid the pagetable
> > lookups and to be more similar to the other arches numa code.
> 
> The vmem_map is only used statically in arch/ia64/mm/init.c, but we use
> the global mem_map for the macros in include/asm-ia64/pgtable.h for
> convenience.  There are a bunch of cases to deal with:
>   o CONFIG_VIRTUAL_MEM_MAP and !CONFIG_VIRTUAL_MEM_MAP
>   o CONFIG_DISCONTIGMEM and !CONFIG_DISCONTIGMEM
>   o any combination of the two above
> 
> We need CONFIG_VIRTUAL_MEM_MAP and CONFIG_DISCONTIGMEM work together at
> the very least so that ia64 generic kernels will work.

Slightly less ugly hack than the ifdefs in generic code is a

#define mem_map vmem_map somewhere in a ia64 header.  The right fix
is to just always use the per-node mem_map.  For SN2 you probably want
a per-node virtual mem_map then.


  parent reply	other threads:[~2003-09-24 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 23:56 [PATCH] discontig patch (work in progress) Jesse Barnes
2003-09-24  1:26 ` Jesse Barnes
2003-09-24  8:43 ` Christoph Hellwig
2003-09-24 14:51 ` Jesse Barnes
2003-09-24 16:54 ` Christoph Hellwig [this message]
2003-09-25 22:54 ` Jesse Barnes
2003-09-26  1:45 ` Jesse Barnes
2003-09-26  1:54 ` Jesse Barnes

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=marc-linux-ia64-106442331327396@msgid-missing \
    --to=hch@infradead.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