All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: .
Date: Fri, 13 Aug 2004 16:02:35 +0000	[thread overview]
Message-ID: <1092412955.4110.22.camel@tdi> (raw)
In-Reply-To: <20040810071417.GA5080@lst.de>

On Fri, 2004-08-13 at 08:29 -0700, Jesse Barnes wrote:
> On Friday, August 13, 2004 2:32 am, Christoph Hellwig wrote:
> > --- /dev/null	Wed Dec 31 16:00:00 196900
> > +++ b/arch/ia64/kernel/numa.c	2004-08-12 18:28:06 -07:00
> > @@ -0,0 +1,46 @@
> > +#include <linux/config.h>
> > +#include <linux/topology.h>
> > +#include <linux/module.h>
> > +#include <asm/processor.h>
> > +#include <asm/smp.h>
> > +
> > +#ifdef CONFIG_NUMA
> >
> > You build this file conditional on CONFIG_
> > UMA, no need for this ifdef.
> 
> Yep, you're right.
> 

   Ok, so you _can_ build NUMA in on a non-SMP kernel and you could even
imagine a single cpu box w/ multiple memory nodes.  I think our code
base should be able to support such a system.  However, for a distro
kernel, the purpose of a UP kernel is to ditch some of the high-end
overhead and tune it for a little box.  What's the performance hit on a
box that doesn't need NUMA/DISCONTIG to turn these on for a UP kernel?
Maybe it's small enough I shouldn't be worried.  Is there any way an
Altix could survive using the virtual memmap code on a UP build?

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


  parent reply	other threads:[~2004-08-13 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  7:14 r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian Christoph Hellwig
2004-08-10 15:51 ` Jesse Barnes
2004-08-12 23:03 ` dann frazier
2004-08-12 23:30 ` Jesse Barnes
2004-08-13  0:07 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: Alex Williamson
2004-08-13  0:14 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian Jesse Barnes
2004-08-13  1:32 ` Jesse Barnes
2004-08-13  9:32 ` Christoph Hellwig
2004-08-13 15:29 ` Jesse Barnes
2004-08-13 16:02 ` Alex Williamson [this message]
2004-08-13 16:16 ` 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=1092412955.4110.22.camel@tdi \
    --to=alex.williamson@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.