From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [ACPI] Re: [DMESG] cpumask_t in action
Date: Fri, 07 Nov 2003 18:13:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106825415027734@msgid-missing> (raw)
On Fri, Nov 07, 2003 at 05:24:56PM +0000, Matthew Wilcox wrote:
> On Fri, Nov 07, 2003 at 09:13:11AM +0100, Sylvain Jeaugey wrote:
> > On Thu, 6 Nov 2003, Matthew Wilcox wrote:
> > 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.
>
> Yes, but do we need to know it at boot time, or should it be available
> in some other way (eg /proc/acpi/srat or something). I would argue
> that is more useful than seeing it in dmesg.
There's also /sys which contains information about which cpus are on
which nodes.
Jesse
reply other threads:[~2003-11-07 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-106825415027734@msgid-missing \
--to=jbarnes@sgi.com \
--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