From: Pavel Machek <pavel@suse.cz>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: Matthew Dobson <colpatch@us.ibm.com>,
Andrew Morton <akpm@zip.com.au>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Martin Bligh <mjbligh@us.ibm.com>,
Andrea Arcangeli <andrea@suse.de>,
Michael Hohnbaum <hohnbaum@us.ibm.com>,
lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: [patch] SImple Topology API v0.3 (1/2)
Date: Wed, 28 Aug 2002 21:29:17 +0200 [thread overview]
Message-ID: <20020828192917.GC10487@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0208280711390.3234-100000@hawkeye.luckynet.adm>
Hi!
> > > - bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
> > > + bool 'Multi-node NUMA system support' CONFIG_X86_NUMA
> >
> > Why not simply CONFIG_NUMA?
>
> Because NUMA is subordinate to X86, and another technology named NUMA
> might appear? Nano-uplinked micro-array... No Ugliness Munched Archive?
> Whatever...
NUMA means non-uniform memory access. At least IBM, AMD and SGI do
NUMA; and I guess anyone with 100+ nodes *has* numa machine. (BUt as
andrea already explained, CONFIG_NUMA is already taken for generic
NUMA support.)
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-08-28 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 19:13 Matthew Dobson
2002-08-22 19:22 ` [Lse-tech] " Christoph Hellwig
2002-08-22 20:41 ` Matthew Dobson
2002-08-22 20:48 ` Christoph Hellwig
2002-08-27 14:31 ` Pavel Machek
2002-08-27 21:18 ` Andrea Arcangeli
2002-08-28 13:14 ` Thunder from the hill
2002-08-28 19:29 ` Pavel Machek [this message]
2002-08-28 20:02 ` Thunder from the hill
2002-08-28 22:31 ` [Lse-tech] " Timothy D. Witham
2002-08-28 22:40 ` Thunder from the hill
2002-08-28 22:42 ` Timothy D. Witham
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=20020828192917.GC10487@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=colpatch@us.ibm.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mjbligh@us.ibm.com \
--cc=thunder@lightweight.ods.org \
--cc=torvalds@transmeta.com \
/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