public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dual or Quad CPU complications?
Date: Sat, 15 Dec 2012 12:49:38 +0100	[thread overview]
Message-ID: <50CC63D2.40903@binarywings.net> (raw)
In-Reply-To: <201212150041.04754.michaelkintzios@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

Am 15.12.2012 01:40, schrieb Mick:
> On Thursday 13 Dec 2012 14:13:56 Bruce Hill wrote:
>> On Thu, Dec 13, 2012 at 08:44:45AM +0100, J. Roeleveld wrote:
>>> NUMA is also an option in the kernel. Should also be fully transparent.
>>> I got one machine with NUMA and only had to set an option for it.
>>>
>>> Does anyone know how to check it's working properly?
>>
>> dmesg | grep NUMA
> 
> Hmm ... it seems that it can't find NUMA configuration:
> 
> $ dmesg | grep UMA
> No NUMA configuration found
> 
> Am I supposed to configure something in userspace?  This is what the kernel 
> has:
> 
> $ uname -a
> Linux dell_xps 3.5.7-gentoo #2 SMP PREEMPT Mon Nov 26 10:36:47 GMT 2012 x86_64 
> Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux
> 
[...]

"dell_xps" as in XPS laptop? There are no NUMA laptops.

Despite all the stuff about terminology, we are basically talking about
multi-socket systems. Things with mainboards like these [1] as opposed
to these [2].

[1] http://www.newegg.com/Product/Product.aspx?Item=N82E16813131378
[2] http://www.newegg.com/Product/Product.aspx?Item=N82E16813131725

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-12-15 11:51 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 [this message]
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
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=50CC63D2.40903@binarywings.net \
    --to=lists@binarywings.net \
    --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