mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Ingo Molnar <mingo@elte.hu>, Ed Tomlinson <tomlins@cam.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] O(1) scheduler-H6/H7/I0 and nice +19
Date: 15 Jan 2002 21:59:38 -0500	[thread overview]
Message-ID: <1011149980.8756.180.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.40.0201151803020.940-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0201151803020.940-100000@blue1.dev.mcafeelabs.com>

On Tue, 2002-01-15 at 21:04, Davide Libenzi wrote:

> On 15 Jan 2002, Robert Love wrote:
> > This isn't a bad idea, as long as we don't use it as a crutch or
> > excuse.  That is, answer scheduling problems with "properly nice your
> > tasks" -- the scheduler should be smart enough, to some degree.
> >
> > FWIW, Solaris actually implements a completely different scheduling
> > policy, SCHED_INTERACT or something.  It is for windowed tasks in X --
> > they get a large interactivity bonus.

> Now ( with 2.5.3-pre1 ) intractivity is *very good* but SCHED_INTERACT
> would help *a lot* to get things even more right.

I looked it up; its called class IA.  I don't know if it grows from a
limitation of their scheduler (i.e. they can't calculate priority and be
as fair to interactive tasks as us) or if it offers a fundamental
advantage.  I suspect their are a myriad of things things we can do with
an interactive/GUI scheduling policy.

One thing this is, since their kernel is preemptible, it marks processes
that very much always deserve a scheduling boost based on interactivity,
and thus their interactivity is quite nice.

	Robert Love


  reply	other threads:[~2002-01-16  2:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0201111723260.3212-100000@localhost.localdomain>
2002-01-11 21:28 ` [patch] O(1) scheduler-H6 " Ed Tomlinson
2002-01-14  3:27   ` [patch] O(1) scheduler-H6/H7 " Ed Tomlinson
2002-01-14  3:45     ` Davide Libenzi
2002-01-15  1:37       ` Ed Tomlinson
2002-01-15  1:50         ` Davide Libenzi
2002-01-15  1:58           ` Davide Libenzi
2002-01-15  2:18           ` Ed Tomlinson
2002-01-15  2:33             ` Davide Libenzi
2002-01-15  3:19               ` Ed Tomlinson
2002-01-15  3:27                 ` Davide Libenzi
2002-01-15 23:48                   ` [patch] O(1) scheduler-H6/H7/I0 " Ed Tomlinson
2002-01-15 23:56                     ` Davide Libenzi
2002-01-16  1:49                     ` Ingo Molnar
2002-01-16  0:44                       ` Ed Tomlinson
2002-01-16  2:48                         ` Ingo Molnar
2002-01-16  1:59                           ` Robert Love
2002-01-16  2:04                             ` Davide Libenzi
2002-01-16  2:59                               ` Robert Love [this message]
2002-01-16  3:04                                 ` Linus Torvalds
2002-01-16  2:06                       ` Rene Rebe
     [not found] <mng==Pine.LNX.4.40.0201151803020.940-100000@blue1.dev.mcafeelabs.com>
     [not found] ` <mng==1011149980.8756.180.camel@phantasy>
2002-01-16 22:41   ` Jens-Uwe Mager

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=1011149980.8756.180.camel@phantasy \
    --to=rml@tech9.net \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tomlins@cam.org \
    --cc=torvalds@transmeta.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

Powered by JetHome