public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Grant <emailgrant@gmail.com>
Subject: Re: [gentoo-user] Dual or Quad CPU complications?
Date: Sat, 15 Dec 2012 18:56:42 +0100	[thread overview]
Message-ID: <2026398.C7IXBk4F5F@localhost> (raw)
In-Reply-To: <CAN0CFw3KtX2VmqNOx5ESGLgiNUJWQZNhW0dcGfaHcxNxU1PonA@mail.gmail.com>

Am Freitag, 14. Dezember 2012, 01:44:26 schrieb Grant:
> > > So if I have 2 physical CPU's with 4 cores each and I enable SMP, I'm
> 
> using
> 
> > > 8 cores?  Can NUMA be either enabled or disabled when using more than
> 
> one
> 
> > > physical CPU, or is it required?
> > 
> > NUMA is a hardware architecture. It's how you access memory on a
> > hardware level: NUMA = Non Uniform Memory Access vs a UMA architecture
> > of typical (old/legacy) SMP systems (UMA = Uniform Memory Access).
> > 
> > In a UMA system, all the memory belongs to all the sockets. In a NUMA
> > system, each socket has it's "own" local memory. In modern (x86-64)
> > processors, each socket has it's own memory controller so each socket
> > controls its own local memory. If one socket runs out of memory it can
> > ask another socket to lend him some memory. In a UMA system, no socket
> > has to ask since memory is global and belongs to all sockets so if one
> > socket uses up all the memory ... the rest "starve". In NUMA, there's
> > more control over who uses what (be it cores or RAM).
> > 
> > If you have a modern dual or quad (or higher #) socket system ...
> > you've got NUMA architecture and you can't get rid of it, it's
> > hardware, not software.
> 
> So I must enable CONFIG_NUMA for more than one physical CPU, and disable it
> for only one physical CPU?

you never need numa for one cpu. Ok?

And even if you have several, you will probably never need it.

-- 
#163933


  parent reply	other threads:[~2012-12-15 17:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13  6:12 [gentoo-user] Dual or Quad CPU complications? Grant
2012-12-13  6:23 ` Alan McKinnon
2012-12-13  7:36   ` Florian Philipp
2012-12-13  7:44     ` J. Roeleveld
2012-12-13 13:01       ` Luis Gustavo Vilela de Oliveira
2012-12-13 13:14         ` Rafa Griman
2012-12-13 14:13       ` Bruce Hill
2012-12-15  0:40         ` Mick
2012-12-15 11:49           ` Florian Philipp
2012-12-14  7:43     ` Grant
2012-12-14  8:47       ` Rafa Griman
2012-12-14  9:44         ` Grant
2012-12-14 10:03           ` Rafa Griman
2012-12-14 22:26             ` Grant
2012-12-15  3:16               ` Grant
2012-12-15  3:25                 ` Michael Mol
2012-12-15 12:40                 ` Florian Philipp
2012-12-15 17:56           ` Volker Armin Hemmann [this message]
2012-12-13 15:55 ` [gentoo-user] " James
2012-12-14  7:53   ` Rafa Griman
2012-12-13 18:18 ` [gentoo-user] " Michael Hampicke
2012-12-13 18:22 ` Volker Armin Hemmann
2012-12-14  7:55   ` Rafa Griman
2012-12-14  8:00     ` Grant
2012-12-15 17:49     ` Volker Armin Hemmann
2012-12-15 19:46       ` Grant
2012-12-15 19:57         ` J. Roeleveld
2012-12-16 12:52           ` Volker Armin Hemmann
2012-12-16 15:39             ` J. Roeleveld
2012-12-16 15:58               ` Michael Mol
2012-12-17  7:00                 ` J. Roeleveld
2012-12-17  9:09                   ` Michael Mol
2012-12-17 10:29                     ` J. Roeleveld

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=2026398.C7IXBk4F5F@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=emailgrant@gmail.com \
    --cc=gentoo-user@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