From: jbarnes-sJ/iWh9BUns@public.gmane.org (Jesse Barnes)
To: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: Sylvain Jeaugey <sylvain.jeaugey-6ktuUTfB/bM@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: [DMESG] cpumask_t in action
Date: Fri, 7 Nov 2003 10:13:15 -0800 [thread overview]
Message-ID: <20031107181315.GA1162@sgi.com> (raw)
In-Reply-To: <20031107172456.GC23754-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
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
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
next prev parent reply other threads:[~2003-11-07 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031105222202.GA24119@sgi.com>
[not found] ` <20031105222202.GA24119-sJ/iWh9BUns@public.gmane.org>
2003-11-06 16:51 ` [DMESG] cpumask_t in action Matthew Wilcox
[not found] ` <20031106165159.GE26869-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 20:11 ` Jes Sorensen
2003-11-07 8:13 ` Sylvain Jeaugey
[not found] ` <Pine.LNX.4.44.0311070907020.29453-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-11-07 17:24 ` Matthew Wilcox
[not found] ` <20031107172456.GC23754-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-11-07 18:13 ` Jesse Barnes [this message]
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=20031107181315.GA1162@sgi.com \
--to=jbarnes-sj/iwh9buns@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sylvain.jeaugey-6ktuUTfB/bM@public.gmane.org \
--cc=willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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