From: Andreas Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.16-rc6-mm2] x86: add NUMA to oops messages
Date: Sun, 18 Jun 2006 18:16:07 +0200 (CEST) [thread overview]
Message-ID: <1364850.1150647367930.SLOX.WebMail.wwwrun@imap-dhs.suse.de> (raw)
In-Reply-To: <200606180815_MC3-1-C2CC-41A5@compuserve.com>
Am So 18.06.2006 14:13 schrieb Chuck Ebbert <76306.1226@compuserve.com>:
> In-Reply-To: <200606181059.44576.ak@suse.de>
>
> On Sun, 18 Jun 2006 10:59:44 +0200, Andi Kleen wrote:
>
> > On Sunday 18 June 2006 10:13, Chuck Ebbert wrote:
> > > Add "NUMA" to x86 oops printouts to help with debugging. Use
> > > vermagic.h
> > > defines to clean up the code, suggested by Arjan van de Ven.
> >
> > I don't see any particular value in printing NUMA here,
>
> It helps a lot when trying to decode oopses posted to the list, as the
> NUMA kernel is very different now that the slab allocator and
> scheduler
> are NUMA-aware.
And there are a thousand other things that change with other
CONFIG_* options. I also can't remember a bug where
this wasn't clear.
In general the rule of thumb is: i386: NUMA is not
used and x86-64 SMP: NUMA is used.
-Andi
next prev parent reply other threads:[~2006-06-18 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 12:13 Chuck Ebbert
2006-06-18 12:48 ` Arjan van de Ven
2006-06-18 17:25 ` Randy.Dunlap
2006-06-18 16:16 ` Andreas Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-18 8:13 Chuck Ebbert
2006-06-18 8:59 ` Andi Kleen
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=1364850.1150647367930.SLOX.WebMail.wwwrun@imap-dhs.suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®