From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: hzhong@cisco.com (Hua Zhong)
Cc: ddade@digitalstatecraft.com, alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org
Subject: Re: Is it bad to have lots of sleeping tasks?
Date: Fri, 24 Aug 2001 22:15:21 +0100 (BST) [thread overview]
Message-ID: <E15aOIT-0006Xa-00@the-village.bc.nu> (raw)
In-Reply-To: <005a01c12cd9$2f153950$103147ab@cisco.com> from "Hua Zhong" at Aug 24, 2001 01:13:04 PM
> So why not do it? Or implement a nicer scheduler? There are many good
> ones. There are o(1) schedulers that provide much better proportional
> sharing. They scale and also perform well even in "few running processes"
> case. They are also not hard to implement (I once implemented such a
> scheduler with 100 lines of patch, and that fitted in the existing Linux
> runqueue framework). What's the resistence to scheduler changes?
The resistance I've seen has been to schedulers that perform more poorly
with < 3 running processes - that being the normal case.
Its also suprisingly hard to find a very simple scheduler that provides
fairness and cache optimal behaviour while working well SMP. Uniprocessor
is easy, uniprocessor with real time isnt too bad, SMP gets tricky.
I'd definitely like to see a better scheduler in the kernel, providing its
as fast for the < 3 processes case too.
Alan
next prev parent reply other threads:[~2001-08-24 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 19:39 Donald Dade
2001-08-24 20:05 ` Alan Cox
2001-08-24 20:13 ` Hua Zhong
2001-08-24 20:32 ` Kurt Garloff
2001-08-24 21:19 ` Alan Cox
2001-08-24 21:15 ` Alan Cox [this message]
[not found] <3B8A88B0.FDCC5ACE@watson.ibm.com>
2001-08-27 19:18 ` Alan Cox
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=E15aOIT-0006Xa-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ddade@digitalstatecraft.com \
--cc=hzhong@cisco.com \
--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
all inboxes | Powered by JetHome®