Re: [gentoo-amd64] Re: amd64 and kernel configuration

[Drew Kirkpatrick <drew.kirkpatrick@gmail.com>]

Just to point out, amd was calling the opterons and such more of a
SUMO configuration (Sufficiently Uniform Memory Organization, not
joking here), instead of NUMA. Whereas technically, it clearly is a
NUMA system, the differences in latency when accessing memory from a
bank attached to another processors memory controller is very small.
Small enough to be largely ignored, and treated like uniform memory
access latencies in a SMP system. Sorta in between SMP unified style
memory access and NUMA. This holds for up to 3 hypertranport link
hops, or up to 8 chips/sockets. You add hypertransport switches to
scale over 8 chips/sockets, it'll most likely be a different story...

What I've always wondered is, the NUMA code in the linux kernel, is
this for handling traditional NUMA, like in a large computer system
(big iron) where NUMA memory access latencies will vary greatly, or is
it simply for optimizing the memory usage across the memory banks.
Keeping data in the memory of the processor using it, etc, etc. Of
course none of this matters for single chip/socket amd systems, as
dual cores as well as single cores share a memory controller. Hmm,
maybe I should drink some coffee and shutup until I'm awake...

On 7/27/05, Duncan <1i5t5.duncan@cox.net> wrote:
> Dulmandakh Sukhbaatar posted <20050727075012.79549.qmail@mail.mng.mn>,
> excerpted below,  on Wed, 27 Jul 2005 15:50:12 +0800:
> 
> > Thanks. How can I enable hypertransport in kernel or somewhere? Anyone
> > knows about NUMA? I read about it, and it seems technology for
> > multiprocessor systems. Thus I have single CPU, I don't need it. Right?
> 
> NUMA is indeed for multi-processor systems.  NUMA is Non-Uniform Memory
> Architecture.  With AMD CPUs that have the memory controller on the same
> chip as the CPU, that means that each CPU can control it's own memory.  If
> you run NUMA mode in this case (and if your BIOS is set up accordingly),
> the kernel will try to keep the memory for each task in the memory handled
> by, local to, that CPU.  If either the kernel or BIOS is set to unified
> memory, or if you only have memory sticks in the slots for one of the
> CPUs, then you won't get NUMA mode and the kernel won't care what memory
> addresses the memory for each process lives at.
> 
> AFAIK, hypertransport is automatically handled by your choice of chipset.
> If the chipset you configure has it, it will be enabled, if not, it won't.
> I was therefore a bit puzzled when you mentioned hypertransport
> specifically in the previous post, since I don't believe there's a
> specific kernel option for it.  (It's possible, however, that there is and
> I've just forgotten about it, since it's been awhile since I reviewed
> the settings for the entire kernel -- I just run make oldconfig and deal
> with any new options in each newer kernel, and additionally do any
> specific tweaking I might want to try.)
> 
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman in
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
> 
> 
> --
> gentoo-amd64@gentoo.org mailing list
> 
>

-- 
gentoo-amd64@gentoo.org mailing list