From: Jes Sorensen <jes@wildopensource.com>
To: Sylvain Jeaugey <sylvain.jeaugey@bull.net>
Cc: Matthew Wilcox <willy@debian.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [DMESG] cpumask_t in action
Date: 10 Nov 2003 03:26:50 -0500 [thread overview]
Message-ID: <yq0brrky6gl.fsf@wildopensource.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311070907020.29453-100000@localhost.localdomain>
>>>>> "Sylvain" == Sylvain Jeaugey <sylvain.jeaugey@bull.net> writes:
Sylvain> These lines show you the numa topology of your machine (in
Sylvain> our case, we have 2 CPUS per domain, and a memory area).
Sylvain> This is quite a big piece of information about hardware. Even
Sylvain> if it is quite long, I think it should be part of the ACPI
Sylvain> information.
Hi Sylvian,
This information is much better exposed through sysfs (/sys) and Andi
Kleen's libnuma, which will also make it visible at runtime to
applications.
Cheers,
Jes
prev parent reply other threads:[~2003-11-10 8:26 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
2003-11-10 8:26 ` Jes Sorensen [this message]
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=yq0brrky6gl.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain.jeaugey@bull.net \
--cc=willy@debian.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