public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] CFS scheduler, -v7
Date: Thu, 3 May 2007 09:45:52 +0200	[thread overview]
Message-ID: <20070503074552.GA14960@elte.hu> (raw)
In-Reply-To: <200704300820.49078.a1426z@gawab.com>


* Al Boldi <a1426z@gawab.com> wrote:

> > i'm pleased to announce release -v7 of the CFS scheduler patchset. 
> > (The main goal of CFS is to implement "desktop scheduling" with as 
> > high quality as technically possible.)
> :
> :
> > As usual, any sort of feedback, bugreport, fix and suggestion is 
> > more than welcome,
> 
> This one seems on par with SD, [...]

excellent :-)

> [...] but there are still some nice issues.
> 
> Try running 3 chew.c's, then renicing one to -10, starves others for 
> some seconds while switching prio-level.  Now renice it back to 10, it 
> starves for up to 45sec.

ok - to make sure i understood you correctly: does this starvation only 
occur right when you renice it (when switching prio levels), and it gets 
rectified quickly once they get over a few reschedules?

> Also, nice levels are only effective on every other step; ie:
>  ... -3/-2 , -1/0 , 1/2 ... yields only 20 instead of 40 prio-levels.

yeah - this is a first-approximation thing.

Some background: in the upstream scheduler (and in SD) nice levels are 
linearly scaled, while in CFS they are exponentially scaled. I did this 
because i believe exponential is more logical: regardless of which nice 
level a task uses, if it goes +2 nice levels up then it will halve its 
"fair CPU share". So for example the CPU consumption delta between nice 
0 and nice +10 is 1/32 - and so is the delta between -5 and +5, -10 and 
-5, etc. This makes nice levels _alot_ more potent than upstream's 
linear approach.

	Ingo

  reply	other threads:[~2007-05-03  7:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30  5:20 [patch] CFS scheduler, -v7 Al Boldi
2007-05-03  7:45 ` Ingo Molnar [this message]
2007-05-03  8:07   ` Ingo Molnar
2007-05-03 11:16     ` Al Boldi
2007-05-03 12:36       ` Ingo Molnar
2007-05-03 13:49         ` Al Boldi
2007-05-03  8:42   ` Al Boldi
2007-05-03 15:02   ` Ting Yang
2007-05-03 15:17     ` Ingo Molnar
2007-05-03 16:00       ` Ting Yang
2007-05-03 19:48         ` Ingo Molnar
2007-05-03 19:57           ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2007-04-28 15:25 Ingo Molnar
2007-04-28 19:20 ` S.Çağlar Onur
2007-04-28 19:24   ` Ingo Molnar
2007-04-28 23:42     ` S.Çağlar Onur
2007-04-29  7:11       ` Ingo Molnar
2007-04-29 12:37         ` S.Çağlar Onur
2007-04-29 15:58           ` Ingo Molnar
2007-04-29 22:29             ` Dennis Brendel
2007-04-30 14:38             ` S.Çağlar Onur
2007-04-28 19:27   ` S.Çağlar Onur
2007-04-29 17:28 ` Prakash Punnoor
2007-05-04 13:05   ` Prakash Punnoor
2007-04-30 16:29 ` Srivatsa Vaddagiri
2007-04-30 18:30 ` Balbir Singh

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=20070503074552.GA14960@elte.hu \
    --to=mingo@elte.hu \
    --cc=a1426z@gawab.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