From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler v17
Date: Sat, 25 Oct 2003 04:10:24 +1000 [thread overview]
Message-ID: <3F996B10.4080307@cyberone.com.au> (raw)
Hi,
http://www.kerneltrap.org/~npiggin/v17/
Still working on SMP and NUMA. Some (maybe) interesting things I put in are
- Sequential CPU balancing so you don't get a big storm of balances
every 1/4s.
- Balancing is trying to err more on the side of caution, I have to start
analysing it more thoroughly though.
- Attacked the NUMA balancing code. There should now be less buslocked ops /
cache pingpongs in some fastpaths. Volanomark likes it, more realistic
loads
won't improve so much http://www.kerneltrap.org/~npiggin/v17/volano.png
This improvement is NUMA only.
I haven't had time to reproduce Cliff's serious reaim performance
dropoffs so
they're probably still there. I couldn't reproduce Martin's kernbench
dropoff,
but the 16-way I'm using only has 512K cache which might not show it up.
next reply other threads:[~2003-10-24 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 18:10 Nick Piggin [this message]
2003-10-24 20:17 ` Nick's scheduler v17 cliff white
2003-10-24 21:49 ` Andrew Theurer
2003-10-25 1:12 ` Nick Piggin
2003-10-26 6:43 ` Nick Piggin
2003-10-27 17:02 ` Andrew Theurer
2003-10-27 23:13 ` Nick Piggin
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=3F996B10.4080307@cyberone.com.au \
--to=piggin@cyberone.com.au \
--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