From: Raphael Jacquot <raphael.jacquot@imag.fr>
To: sander@humilis.net
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Sergey S. Kostyliov" <rathamahata@ehouse.ru>
Subject: Re: NUMA or not on dual Opteron
Date: Thu, 13 Jan 2005 11:02:19 +0100 [thread overview]
Message-ID: <41E6472B.5020701@imag.fr> (raw)
In-Reply-To: <20050113094537.GB2547@favonius>
Sander wrote:
> Linus Torvalds wrote (ao):
>
>>On Wed, 12 Jan 2005, Sergey S. Kostyliov wrote:
>>
>>>2.6.10-rc1 hangs at boot stage for my dual opteron machine
>>
>>Oops, yes. There's some recent NUMA breakage - either disable
>>CONFIG_NUMA, or apply the patches that Andi Kleen just posted on the
>>mailing list (the second option much preferred, just to verify that
>>yes, that does fix it).
>
>
> I was under the impression that NUMA is useful on > 2-way systems only.
> Is this true, and if not, under what circumstances is NUMA useful on
> 2-way Opteron systems?
>
> In other words: why should one want NUMA to be enabled or disabled for
> dual Opteron?
>
> Thanks in advance.
>
Numa needs to be enabled on bi-opteron systems because each processor
controls part of the memory. unlike the intel memory architecture, where
processors share the same bus to access memory.
Numa in opteron systems is thus required to allow sharing of memory .
next prev parent reply other threads:[~2005-01-13 10:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 5:09 Linux 2.6.11-rc1 Linus Torvalds
2005-01-12 7:07 ` Keith Owens
2005-01-12 7:32 ` Markus Trippelsdorf
2005-01-13 22:37 ` Linux 2.6.11-rc1 (ACPI related problems) Hanspeter Kunz
2005-01-12 8:24 ` Linux 2.6.11-rc1 Brice Goglin
2005-01-12 9:20 ` Tino Keitel
2005-01-12 9:38 ` Brice Goglin
2005-01-12 14:13 ` Dmitry Torokhov
2005-01-12 14:35 ` Brice Goglin
2005-01-12 15:50 ` Linus Torvalds
2005-01-12 19:13 ` Vojtech Pavlik
2005-01-12 15:24 ` Sergey S. Kostyliov
2005-01-12 15:32 ` Linus Torvalds
2005-01-12 15:44 ` Gene Heskett
2005-01-12 16:03 ` Sergey S. Kostyliov
2005-01-13 9:45 ` NUMA or not on dual Opteron (was: Re: Linux 2.6.11-rc1) Sander
2005-01-13 10:02 ` Raphael Jacquot [this message]
2005-01-13 17:07 ` NUMA or not on dual Opteron Justin M. Forbes
2005-01-13 19:43 ` Andi Kleen
2005-01-13 19:40 ` Andi Kleen
2005-01-13 15:36 ` NUMA or not on dual Opteron (was: Re: Linux 2.6.11-rc1) Alan Cox
2005-01-13 19:38 ` NUMA or not on dual Opteron Andi Kleen
2005-01-15 23:42 ` Sander
2005-01-13 21:24 ` Bernd Eckenfels
2005-01-14 8:04 ` David Schwartz
2005-01-14 8:10 ` Arjan van de Ven
2005-01-14 8:48 ` Andi Kleen
2005-01-12 19:06 ` Linux 2.6.11-rc1 -- usb_storage and Genesys Jan De Luyck
2005-01-13 5:42 ` [PATCH] contort getdents64 to pacify gcc-2.96 Adam Kropelin
2005-01-13 3:51 ` Linus Torvalds
2005-01-13 23:15 ` Linux 2.6.11-rc1 (compile stats) John Cherry
2005-01-16 9:22 ` Cross-compilation broken (was: Re: Linux 2.6.11-rc1) Geert Uytterhoeven
2005-01-16 16:09 ` Sam Ravnborg
2005-01-17 9:00 ` Geert Uytterhoeven
2005-01-19 21:07 ` Linux 2.6.11-rc1 Daniel Gryniewicz
2005-01-20 4:16 ` Dmitry Torokhov
2005-01-20 4:49 ` Daniel Gryniewicz
2005-01-20 7:17 ` Peter Osterlund
2005-01-20 15:01 ` Romano Giannetti
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=41E6472B.5020701@imag.fr \
--to=raphael.jacquot@imag.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@ehouse.ru \
--cc=sander@humilis.net \
/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