From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] (0/3) NUMA aware scheduler
Date: Thu, 16 Jan 2003 10:27:23 -0800 [thread overview]
Message-ID: <2050000.1042741643@flay> (raw)
Following is a sequence of patches to add NUMA awareness to the scheduler.
These have been submitted to you several times before, but in my opinion
were structured in such a way to make them too invasive to non-NUMA machines.
I propsed a new scheme of working in "concentric circles" which this set
follows (Erich did most of the hard work of restructuring), and is now
completely non-invasive to non-NUMA systems. It has no effect whatsoever
on standard machines. This can be seen by code inspection, and has been
checked by benchmarking.
These patches are the culmination of work by Erich Focht, Michael Hohnbaum
and myself. We've also incorporated feedback from Christoph and Robert Love.
I believe these are now ready for mainline acceptance. I've tested them on
NUMA-Q, standard SMP and UP. Erich has run them on the NEC ia64 NUMA machine.
Benchmarks on a 16-way NUMA-Q machine w/ 16Gb of RAM
Kernbench: (average of 5 kernel compiles)
Elapsed User System CPU
2.5.58 20.012s 191.81s 48.37s 1200.6%
2.5.58-numasched 19.57s 187.264s 42.186s 1171.8%
NUMA schedbench 64: (64 processes running memory allocation fairly heavily)
Elapsed TotalUser TotalSys
2.5.48 608.81 9418.37 26.74
2.5.58-numasched 230.49 3613.47 15.57
next reply other threads:[~2003-01-16 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 18:27 Martin J. Bligh [this message]
2003-01-16 19:32 ` [PATCH] (0/3) NUMA aware scheduler Martin J. Bligh
2003-01-16 19:48 ` Andrew Theurer
2003-01-19 22:04 ` Pavel Machek
2003-01-16 20:28 ` Linus Torvalds
2003-01-16 22:36 ` 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=2050000.1042741643@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--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