public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc5-mm2 :-)
Date: Tue, 13 Dec 2005 23:16:11 +1100	[thread overview]
Message-ID: <200512132316.14118.kernel@kolivas.org> (raw)
In-Reply-To: <1916802326.20051213121330@dns.toxicfilms.tv>

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

On Tuesday 13 December 2005 22:13, Maciej Soltysiak wrote:
> Hello Con,
>
> Tuesday, December 13, 2005, 6:52:09 AM, you wrote:
> > I missed this announcement (been on leave for a while). This SCHED_BATCH
> > implementation is by Ingo and it it is not "idle" scheduling as I have
> > implemented in the staircase scheduler. This is just to restrict a task
> > to not having any interactive bonus at any stage and to have predictable
> > scheduling behaviour I guess.
>
> Thanks a lot. That's good anyway.
>
> If I understand correctly, if Ingo's version gets merged with linus' tree
> your implementions of SCHED_BATCH in -ck will be replacing the one from
> Ingo.

Yes. SCHED_BATCH in Ingo's implementation is more like turning off the 
interactive setting in staircase, and the idle scheduling staircase offers is 
extremely useful.

> A silly question. Is SCHED_BATCH-kind-of-thing a standard in Unices or
> general operating system engineering know-how? Or is this concept only
> available for Linux?

Fairly standard in Unices but prone to all sorts of priority inversion 
starvation scenarios so very few implement it. In freebsd for example you can 
use their idle scheduling only if you are root to prevent this starvation - 
which kind of makes it useless in practice. My implementation is fairly 
robust at avoiding the priority inversion problem - at least I haven't seen a 
bug report about it for years since I address it :)

Cheers,
Con

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-12-13 12:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 12:13 2.6.15-rc5-mm2 Andrew Morton
2005-12-11 12:39 ` 2.6.15-rc5-mm2 Benoit Boissinot
2005-12-11 15:17 ` 2.6.15-rc5-mm2 Benoit Boissinot
2005-12-11 15:47 ` 2.6.15-rc5-mm2 Rafael J. Wysocki
2005-12-11 15:52   ` 2.6.15-rc5-mm2: broken resume from disk on x86-64 Rafael J. Wysocki
2005-12-11 16:02   ` 2.6.15-rc5-mm2: evdev problem Rafael J. Wysocki
2005-12-11 18:22     ` Dmitry Torokhov
2005-12-11 16:06   ` 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes Rafael J. Wysocki
2005-12-11 20:38     ` Andrew Morton
2005-12-12 19:53       ` Rafael J. Wysocki
2005-12-12 20:29         ` Andrew Morton
2005-12-12 20:55           ` Rafael J. Wysocki
2005-12-12 21:09             ` Andrew Morton
2005-12-12 21:39               ` Rafael J. Wysocki
2005-12-12 21:47                 ` Andrew Morton
2005-12-12 21:56                 ` Ben Pfaff
2005-12-13  6:52           ` [linux-usb-devel] " David Brownell
2005-12-13 22:10             ` Rafael J. Wysocki
2005-12-13 22:22               ` David Brownell
2005-12-13 22:39                 ` Rafael J. Wysocki
2005-12-13 23:31                   ` David Brownell
2005-12-11 16:08 ` 2.6.15-rc5-mm2 Jesper Juhl
2005-12-11 21:13   ` [PATCH] Fix vesafb display panning regression Antonino A. Daplas
2005-12-11 21:30     ` Jesper Juhl
2005-12-11 16:12 ` 2.6.15-rc5-mm2 :-) Maciej Soltysiak
2005-12-13  5:52   ` Con Kolivas
     [not found]     ` <1916802326.20051213121330@dns.toxicfilms.tv>
2005-12-13 12:16       ` Con Kolivas [this message]
2005-12-13 23:30         ` Peter Williams
2005-12-11 17:56 ` 2.6.15-rc5-mm2: two cs5535 modules Adrian Bunk
2005-12-12 18:29   ` Ben Gardner
2005-12-12 22:49     ` Alan Cox
2005-12-12  0:53 ` 2.6.15-rc5-mm2 Grant Coady
2005-12-12 14:05 ` 2.6.15-rc5-mm2 Cornelia Huck
2005-12-14  8:54 ` SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2] J.A. Magallon
     [not found]   ` <20060120192259.4460af42.akpm@osdl.org>
2006-01-21 23:46     ` J.A. Magallon
2006-01-22  0:22       ` Randy.Dunlap
2005-12-15 13:41 ` 2.6.15-rc5-mm2 Reuben Farrelly

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=200512132316.14118.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solt2@dns.toxicfilms.tv \
    /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