public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: amd64 and kernel configuration
Date: Wed, 27 Jul 2005 03:13:14 -0700	[thread overview]
Message-ID: <pan.2005.07.27.10.13.13.844736@cox.net> (raw)
In-Reply-To: 20050727075012.79549.qmail@mail.mng.mn

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



  parent reply	other threads:[~2005-07-27 10:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  6:29 [gentoo-amd64] amd64 and kernel configuration Dulmandakh Sukhbaatar
2005-07-27  6:10 ` [gentoo-amd64] " Duncan
2005-07-27  6:19   ` NY Kwok
2005-07-27  7:50     ` Dulmandakh Sukhbaatar
2005-07-27  7:04       ` Michal Žeravík
2005-07-27  9:58         ` netpython
2005-07-27 12:30           ` Brett Johnson
2005-07-27 15:58             ` [gentoo-amd64] " Duncan
2005-07-27 10:02         ` Duncan
2005-07-27 10:13       ` Duncan [this message]
2005-07-27 10:27         ` [gentoo-amd64] " Paolo Ripamonti
2005-07-27 14:19           ` [gentoo-amd64] " Duncan
2005-07-27 14:31             ` Paolo Ripamonti
2005-07-27 16:16               ` [gentoo-amd64] " Duncan
2005-07-27 10:46         ` [gentoo-amd64] " Drew Kirkpatrick
2005-07-27 15:42           ` [gentoo-amd64] " Duncan
2005-07-27 17:07             ` Jean.Borsenberger
2005-07-27 10:18     ` Duncan

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=pan.2005.07.27.10.13.13.844736@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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