public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] IA64: Sparse and Discontig Mem need NUMA
Date: Thu, 03 May 2007 01:26:35 +0000	[thread overview]
Message-ID: <20070503012633.GB3630@verge.net.au> (raw)
In-Reply-To: <20070502082716.GA6689@verge.net.au>

On Wed, May 02, 2007 at 09:22:58AM -0700, Luck, Tony wrote:
> > This seems line an issue best solved by prohibiting such settings through
> > Kconfig. But if it is desirable for sparse and discontig memory to work
> > without CONFIG_NUMA let me know and I'll have a stab at it. It does seem
> > possible code-wise. I'm just not sure if its useful.
> 
> I pretty sure that we used to be able to build for a DISCONTIG but
> non-NUMA system ... this is a quite common case, systems with >4G
> of memory put the first 2G at 0-2G, reserve the 2G-4G area for
> PCI memory mapped devices (and other platform specific stuff) then
> the rest of RAM is at some >4G address.  With just a 2G hole it
> is possible to paper over it, but some systems put the extra
> memory at much higher addresses.

I did take a look at what it would take to allow Sparse to compile
in non-NUMA. It seemed that Sparse was very much centered around NUMA
so I wondered how useful the result might be. I will take a look
into Discontig and see what is required there.

> But it would be nice to reduce the CONFIG maze ... so perhaps we
> should ponder what overhead such a system would suffer by having
> to be built as CONFIG_NUMA=y.  If this is small, then perhaps we
> can simplify things.

I guess it might be a bit tricky to measure that comprehensively.
But it would certainly make things easier. I think that the patch
I sent implements what you are suggesting, though perhaps it isn't
exactly what you had in mind.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


      parent reply	other threads:[~2007-05-03  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  8:27 [PATCH] IA64: Sparse and Discontig Mem need NUMA Simon Horman
2007-05-02 16:22 ` Luck, Tony
2007-05-03  1:26 ` Simon Horman [this message]

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=20070503012633.GB3630@verge.net.au \
    --to=horms@verge.net.au \
    --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