From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>,
ricklind@us.ibm.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: NUMA scheduler broken
Date: Fri, 07 Mar 2003 00:30:30 -0800 [thread overview]
Message-ID: <324180000.1047025830@[10.10.2.4]> (raw)
Something in current -bk breaks the NUMA scheduler.
Kernbench: (make -j N vmlinux, where N = 16 x num_cpus)
Elapsed System User CPU
2.5.64-align 46.29 129.38 567.02 1504.75
2.5.64-bk 153.04 49.05 558.30 395.00
Looks like it's not node-balancing at all and just using one node.
However, I spent a few minutes looking, and can't see anything obvious
that would have caused it.
Will look at it some more tommorow when I wake up, but if any of you
can see what's broken of the top of your head ...
M.
next reply other threads:[~2003-03-07 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 8:30 Martin J. Bligh [this message]
2003-03-07 11:51 ` NUMA scheduler broken Rick Lindsley
2003-03-07 12:41 ` Ingo Molnar
2003-03-07 16:24 ` Martin J. Bligh
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='324180000.1047025830@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ricklind@us.ibm.com \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).