From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [DMESG] cpumask_t in action
Date: Fri, 07 Nov 2003 17:24:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106825306426816@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106807117402763@msgid-missing>
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.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-11-07 17:24 UTC|newest]
Thread overview: 37+ 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
2003-11-07 17:24 ` Matthew Wilcox [this message]
2003-11-10 8:26 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 18:56 Luck, Tony
2003-11-06 20:31 ` Robin Holt
2003-11-07 2:06 ` Paul Jackson
2003-11-06 17:09 Daniel Blueman
2003-11-05 23:18 Chen, Kenneth W
2003-11-05 23:24 ` Jesse Barnes
2003-11-05 23:42 ` Antonio Vargas
2003-11-06 4:36 ` Jesse Barnes
2003-11-05 22:22 Jesse Barnes
2003-11-05 22:49 ` Jesse Barnes
2003-11-05 23:56 ` Peter Chubb
[not found] ` <20031105222202.GA24119-sJ/iWh9BUns@public.gmane.org>
2003-11-06 16:51 ` Matthew Wilcox
2003-11-06 16:51 ` Matthew Wilcox
[not found] ` <20031106165159.GE26869-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 20:11 ` Jes Sorensen
2003-11-06 20:11 ` Jes Sorensen
2003-11-07 8:13 ` Sylvain Jeaugey
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
2003-11-07 17:24 ` Matthew Wilcox
2003-11-10 8:26 ` Jes Sorensen
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-106825306426816@msgid-missing \
--to=willy@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.