From: Muli Ben-Yehuda <mulix@mulix.org>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler: Process priority fed back to parent?
Date: Tue, 16 Mar 2004 18:02:46 +0200 [thread overview]
Message-ID: <20040316160246.GL28008@mulix.org> (raw)
In-Reply-To: <40572922.10109@techsource.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Tue, Mar 16, 2004 at 11:19:46AM -0500, Timothy Miller wrote:
> Unfortunately, the OS has to play babysitter to processes, because
> they're guaranteed to misbehave. Preemption exists to ensure fairness
> amongst processes. Thus, while you're right that it would be nice to
> have processes report their CPU requirements, if we were to actually DO
> that, it would be a disaster.
I agree we should do the best thing possible without any prior
knowledge of what a process should do. I don't agree we should add
pointless complexity to the scheduler for dubious gains (getting rid
of the very short ramp up time). Of course, if you think it's useful,
feel free to implement it and let's resume the discussion when we have
some numbers.
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-16 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 15:16 Scheduler: Process priority fed back to parent? Timothy Miller
2004-03-16 15:46 ` Muli Ben-Yehuda
2004-03-16 16:19 ` Timothy Miller
2004-03-16 16:02 ` Muli Ben-Yehuda [this message]
2004-03-16 16:55 ` Timothy Miller
2004-03-16 18:49 ` Horst von Brand
2004-03-25 14:16 ` Pavel Machek
2004-03-16 16:06 ` Eric
2004-03-16 16:46 ` Timothy Miller
2004-03-16 19:23 ` Eric
2004-03-16 21:35 ` Timothy Miller
2004-03-16 23:05 ` Eric
2004-03-18 2:55 ` David Schwartz
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=20040316160246.GL28008@mulix.org \
--to=mulix@mulix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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