From: Bill Davidsen <davidsen@tmr.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] generalise scheduling classes
Date: Tue, 25 Nov 2003 11:23:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1031125111256.4037B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <3FC2B487.8080709@cyberone.com.au>
On Tue, 25 Nov 2003, Nick Piggin wrote:
>
>
> bill davidsen wrote:
>
> >In article <3FC0A0C2.90800@cyberone.com.au>,
> >Nick Piggin <piggin@cyberone.com.au> wrote:
> >
> >| We still don't have an HT aware scheduler, which is unfortunate because
> >| weird stuff like that looks like it will only become more common in future.
> >
> >The idea is hardly new, in the late 60's GE (still a mainframe vendor at
> >that time) was looking at two execution units on a single memory path.
> >They decided it would have problems with memory bandwidth, what else is
> >new?
> >
>
> I don't think I said new, but I guess they (SMT, NUMA, CMP) are newish
> for architectures supported by Linux Kernel. OK NUMA has been around for
> a while, but the scheduler apparently doesn't work so well for atypical
> new NUMAs like Opteron.
You didn't say new, I wasn't correcting you, just thought that the
historical perspective might be interesting. I would love to try the new
scheduler, but my test computer is not pleased with Fedora.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-11-25 16:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031117021511.GA5682@averell>
[not found] ` <3FB83790.3060003@cyberone.com.au>
[not found] ` <20031117141548.GB1770@colin2.muc.de>
[not found] ` <Pine.LNX.4.56.0311171638140.29083@earth>
[not found] ` <20031118173607.GA88556@colin2.muc.de>
[not found] ` <Pine.LNX.4.56.0311181846360.23128@earth>
[not found] ` <20031118235710.GA10075@colin2.muc.de>
[not found] ` <3FBAF84B.3050203@cyberone.com.au>
[not found] ` <501330000.1069443756@flay>
[not found] ` <3FBF099F.8070403@cyberone.com.au>
[not found] ` <1010800000.1069532100@[10.10.2.4]>
[not found] ` <3FC01817.3090705@cyberone.com.au>
2003-11-23 11:57 ` [RFC] generalise scheduling classes Nick Piggin
2003-11-23 12:01 ` Ingo Molnar
2003-11-23 12:15 ` Nick Piggin
2003-11-23 12:21 ` Ingo Molnar
2003-11-23 16:26 ` Martin J. Bligh
2003-12-01 10:08 ` [patch] sched-HT-2.6.0-test11-A5 Ingo Molnar
2003-12-06 19:01 ` Martin J. Bligh
2003-12-06 21:40 ` Zwane Mwaikambo
2003-12-07 13:34 ` Ingo Molnar
2003-12-07 16:39 ` Anton Blanchard
2003-12-07 17:16 ` Martin J. Bligh
2003-12-07 18:31 ` Zwane Mwaikambo
2003-12-07 20:17 ` Anton Blanchard
2003-12-08 17:57 ` Ingo Molnar
2003-12-07 17:22 ` Anton Blanchard
2003-12-08 17:56 ` William Lee Irwin III
2003-12-08 18:21 ` Ingo Molnar
2003-12-08 19:12 ` William Lee Irwin III
2003-12-08 22:20 ` age
2003-12-08 19:36 ` William Lee Irwin III
2003-11-23 21:38 ` [RFC] generalise scheduling classes William Lee Irwin III
2003-11-24 2:19 ` Nick Piggin
2003-11-24 1:06 ` Anton Blanchard
2003-11-24 2:26 ` Nick Piggin
2003-11-24 2:39 ` Davide Libenzi
2003-11-24 22:48 ` bill davidsen
2003-11-25 1:46 ` Nick Piggin
2003-11-25 16:23 ` Bill Davidsen [this message]
2003-11-30 9:35 ` [RFC] Further SMP / NUMA scheduler improvements 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=Pine.LNX.3.96.1031125111256.4037B-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.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;
as well as URLs for NNTP newsgroup(s).