From: Nick Piggin <piggin@cyberone.com.au>
To: Ian Kumlien <pomac@vapor.com>
Cc: Con Kolivas <kernel@kolivas.org>,
Daniel Phillips <phillips@arcor.de>,
linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net>
Subject: Re: [SHED] Questions.
Date: Wed, 03 Sep 2003 09:49:04 +1000 [thread overview]
Message-ID: <3F552C70.2030109@cyberone.com.au> (raw)
In-Reply-To: <1062523374.5171.321.camel@big.pomac.com>
Ian Kumlien wrote:
>On Tue, 2003-09-02 at 13:08, Nick Piggin wrote:
>
>>Ian Kumlien wrote:
>>
>>>You could say that the problem the current scheduler has is that it's
>>>not allowed to starve anything, thats why we add stuff to give
>>>interactive bonus. But if it *was* allowed to starve but gave bonus to
>>>the starved processes that would make most of the interactive detection
>>>useless (yes, we still need the "didn't use their timeslice" bit and
>>>with a timeslice that gets smaller the higher the pri we'd automagically
>>>balance most processes).
>>>
>>>(As usual my assumptions might be really wrong...)
>>>
>>First off, no general purpose scheduler should allow starvation depending
>>on your definition. The interactivity stuff, and even dynamic priorities
>>allow short term unfairness.
>>
>
>When you reach a certain load you *have to* allow starvation. Ie, you
>can't work around it... All i say is that if we have a more relaxed
>method we might benefit from it.
>
Depending on your definition. If 1000 processes get 10ms CPU every
10000ms I would not call that being starved. Maybe thats misleading.
>
>>Hmm... what else? The "didn't use their timeslice" thing is not
>>applicable: a new timeslice doesn't get handed out until the previous one
>>is used. The priorities thing is done based on how much sleeping the
>>process does.
>>
>
>And not the amount of cpu consumed by the app / go?
>
Well yeah in a way. Consuming CPU lowers priority, sleeping raises.
>
>>Its funny, everyone seems to have very similar ideas that they are
>>expressing by describing different implementations they have in mind.
>>
>
>Yes =), I'm mailing Con directly now as well, to save some unwanted
>traffic here =). I just hope that we'll reach a agreement somewhere
>about whats sane or not...
>
>Mail me if you're interested as well.
>
OK CC me
next prev parent reply other threads:[~2003-09-02 23:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 10:07 [SHED] Questions Ian Kumlien
2003-08-31 10:17 ` Nick Piggin
2003-08-31 10:24 ` Ian Kumlien
2003-08-31 10:41 ` Nick Piggin
2003-08-31 10:46 ` Nick Piggin
[not found] ` <1062326980.9959.65.camel@big.pomac.com>
[not found] ` <3F51D4A4.4090501@cyberone.com.au>
2003-08-31 11:08 ` Ian Kumlien
2003-08-31 11:31 ` Nick Piggin
2003-08-31 11:43 ` Ian Kumlien
2003-08-31 18:53 ` Robert Love
2003-08-31 19:31 ` Ian Kumlien
2003-08-31 19:51 ` Robert Love
2003-08-31 22:41 ` Ian Kumlien
2003-08-31 23:41 ` Robert Love
2003-09-01 0:00 ` Ian Kumlien
2003-09-01 2:50 ` Con Kolivas
2003-09-01 15:58 ` Antonio Vargas
2003-09-01 22:19 ` Ian Kumlien
2003-09-01 4:03 ` Robert Love
2003-09-01 5:07 ` Con Kolivas
2003-09-01 5:55 ` Robert Love
2003-09-01 22:24 ` Ian Kumlien
2003-09-01 14:21 ` Antonio Vargas
2003-09-01 19:36 ` Geert Uytterhoeven
2003-09-01 22:49 ` Ian Kumlien
2003-09-01 15:07 ` Daniel Phillips
2003-09-01 14:16 ` Antonio Vargas
2003-09-01 23:03 ` Ian Kumlien
2003-09-02 0:04 ` Nick Piggin
2003-09-02 0:23 ` Con Kolivas
2003-09-02 10:25 ` Ian Kumlien
2003-09-02 11:08 ` Nick Piggin
2003-09-02 17:22 ` Ian Kumlien
2003-09-02 23:49 ` Nick Piggin [this message]
2003-09-03 23:02 ` Ian Kumlien
2003-09-04 1:39 ` Mike Fedyk
2003-09-02 10:44 ` Wes Janzen
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=3F552C70.2030109@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=pomac@vapor.com \
--cc=rml@tech9.net \
/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).