From: Sylvain Jeaugey <sylvain.jeaugey@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [DMESG] cpumask_t in action
Date: Fri, 07 Nov 2003 08:13:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106824271316473@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106807117402763@msgid-missing>
On Thu, 6 Nov 2003, Matthew Wilcox wrote:
> > ACPI: SRAT Processor (id[0x00] eid[0x00]) in proximity domain 0 enabled
> > ACPI: SRAT Processor (id[0x20] eid[0x00]) in proximity domain 0 enabled
[...]
> > ACPI: SRAT Processor (id[0x00] eid[0x5e]) in proximity domain 47 enabled
> > ACPI: SRAT Processor (id[0x20] eid[0x5e]) in proximity domain 47 enabled
>
> ... for example ;-) 96 lines which honestly tell me nothing.
>
> > ACPI: SRAT Memory (0x0000003000000000 length 0x0000001000000000 type 0x1) in proximity domain 0 enabled
> > ACPI: SRAT Memory (0x000000b000000000 length 0x0000001000000000 type 0x1) in proximity domain 1 enabled
> [ snip 44 lines ]
> > ACPI: SRAT Memory (0x0000173000000000 length 0x0000001000000000 type 0x1) in proximity domain 46 enabled
> > ACPI: SRAT Memory (0x000017b000000000 length 0x0000001000000000 type 0x1) in proximity domain 47 enabled
>
> ... and again.
>
These lines show you the numa topology of your machine (in our case, we
have 2 CPUS per domain, and a memory area).
This is quite a big piece of information about hardware. Even if it is
quite long, I think it should be part of the ACPI information.
Sylvain
next prev parent reply other threads:[~2003-11-07 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 22:22 [DMESG] cpumask_t in action Jesse Barnes
2003-11-05 23:18 ` Chen, Kenneth W
2003-11-06 16:51 ` Matthew Wilcox
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 18:56 ` Luck, Tony
2003-11-06 20:11 ` Jes Sorensen
2003-11-06 20:31 ` Robin Holt
2003-11-07 2:06 ` Paul Jackson
2003-11-07 8:13 ` Sylvain Jeaugey [this message]
2003-11-07 17:24 ` Matthew Wilcox
2003-11-10 8:26 ` Jes Sorensen
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=marc-linux-ia64-106824271316473@msgid-missing \
--to=sylvain.jeaugey@bull.net \
--cc=linux-ia64@vger.kernel.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