From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Roland Dreier <roland@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: runnable tasks never making it to a runqueue where they can run?
Date: Wed, 07 Mar 2012 17:31:45 +0100 [thread overview]
Message-ID: <1331137905.11248.355.camel@twins> (raw)
In-Reply-To: <CAL1RGDUbxcx+cCM_mf1nFJ=Jz0SyaiW0ffxiY4gZ6KNWzJCnMg@mail.gmail.com>
On Tue, 2012-03-06 at 18:19 -0800, Roland Dreier wrote:
> 6,7,8,10,18,19,22 but never onto 23
> (Interestingly, those 8 CPUs seem to form a domain)
That would be 'interesting'... I have a similar wsm box and you should
have a domain setup like:
0-5,12-17 (node 0)
6-11,18-23 (node 1)
Where the first set (0-5 & 6-11) is smt0 and the second set (12-17 &
18-23) smt1.
Can you boot with sched_debug and send me both /proc/cpuinfo and dmesg?
next prev parent reply other threads:[~2012-03-07 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 2:19 runnable tasks never making it to a runqueue where they can run? Roland Dreier
2012-03-07 16:30 ` Peter Zijlstra
2012-03-07 16:31 ` Peter Zijlstra [this message]
2012-03-07 18:03 ` Roland Dreier
2012-03-08 10:28 ` Peter Zijlstra
2012-03-08 11:55 ` Srivatsa Vaddagiri
2012-03-08 12:00 ` Peter Zijlstra
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=1331137905.11248.355.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@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