From: Anton Blanchard <anton@samba.org>
To: linux-kernel@vger.kernel.org
Cc: nickpiggin@yahoo.com.au, nathanl@austin.ibm.com, jbarnes@sgi.com
Subject: sched_domains + NUMA issue
Date: Sun, 29 Aug 2004 21:18:55 +1000 [thread overview]
Message-ID: <20040829111855.GB26072@krispykreme> (raw)
Hi,
We are seeing errors in the sched domains debug code when SMT + NUMA is
enabled. Nathan pointed out that the recent change to limit the number
of nodes in a scheduling group may be causing this - in particular
sched_domain_node_span.
It looks like ia64 are the only ones implementing a reasonable
node_distance, the others just do:
#define node_distance(from,to) (from != to)
On these architectures I wonder if we should disable the
sched_domain_node_span code since we will just get a random grouping of
cpus.
Anton
CPU0: online
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
domain 2: span 00000000,00000000,00000000,000f0003
groups: 00000000,00000000,00000000,00000003 00000000,00000000,00000000,000f0000
CPU1: online
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000001
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
ERROR parent span is not a superset of domain->span
domain 2: span 00000000,00000000,00000000,000f0000
ERROR domain->span does not contain CPU1
groups: 00000000,00000000,00000000,00000003 00000000,00000000,00000000,000f0000
ERROR groups don't span domain->span
CPU16: online
domain 0: span 00000000,00000000,00000000,00030000
groups: 00000000,00000000,00000000,00010000 00000000,00000000,00000000,00020000
domain 1: span 00000000,00000000,00000000,000f0000
groups: 00000000,00000000,00000000,00030000 00000000,00000000,00000000,000c0000
domain 2: span 00000000,00000000,00000000,000f0003
groups: 00000000,00000000,00000000,000f0000 00000000,00000000,00000000,00000003
CPU17: online
domain 0: span 00000000,00000000,00000000,00030000
groups: 00000000,00000000,00000000,00020000 00000000,00000000,00000000,00010000
domain 1: span 00000000,00000000,00000000,000f0000
groups: 00000000,00000000,00000000,00030000 00000000,00000000,00000000,000c0000
domain 2: span 00000000,00000000,00000000,000f0000
groups: 00000000,00000000,00000000,000f0000 00000000,00000000,00000000,00000003
ERROR groups don't span domain->span
CPU18: online
domain 0: span 00000000,00000000,00000000,000c0000
groups: 00000000,00000000,00000000,00040000 00000000,00000000,00000000,00080000
domain 1: span 00000000,00000000,00000000,000f0000
groups: 00000000,00000000,00000000,000c0000 00000000,00000000,00000000,00030000
ERROR parent span is not a superset of domain->span
domain 2: span 00000000,00000000,00000000,00000000
ERROR domain->span does not contain CPU18
groups: 00000000,00000000,00000000,000f0000 00000000,00000000,00000000,00000003
ERROR groups don't span domain->span
CPU19: online
domain 0: span 00000000,00000000,00000000,000c0000
groups: 00000000,00000000,00000000,00080000 00000000,00000000,00000000,00040000
domain 1: span 00000000,00000000,00000000,000f0000
groups: 00000000,00000000,00000000,000c0000 00000000,00000000,00000000,00030000
ERROR parent span is not a superset of domain->span
domain 2: span 00000000,00000000,00000000,00000000
ERROR domain->span does not contain CPU19
groups: 00000000,00000000,00000000,000f0000 00000000,00000000,00000000,00000003
ERROR groups don't span domain->span
next reply other threads:[~2004-08-29 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 11:18 Anton Blanchard [this message]
2004-08-29 16:40 ` Jesse Barnes
2004-08-29 16:48 ` William Lee Irwin III
2004-08-30 21:34 ` NUMA for abstract bus-masters (was Re: sched_domains + NUMA issue) Guennadi Liakhovetski
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=20040829111855.GB26072@krispykreme \
--to=anton@samba.org \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=nickpiggin@yahoo.com.au \
/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®