public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler v19a
Date: Sun, 16 Nov 2003 00:11:36 +1100	[thread overview]
Message-ID: <3FB62608.4010708@cyberone.com.au> (raw)

http://www.kerneltrap.org/~npiggin/v19a/

So the previous didn't exactly improve interactivity.

This one seems to be better. Major thing is microsecond timeslice
accounting. Other small fixes related to the microsecond stuff.
No idea what this has done to context switch and wake up performance,
but it should be able to be improved a bit.

I've made patches for Linus and Andrew's trees.


             reply	other threads:[~2003-11-15 13:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 13:11 Nick Piggin [this message]
2003-11-20 20:45 ` Nick's scheduler v19a Markus Hästbacka
2003-11-20 23:34   ` Nick Piggin
2003-11-21  6:11     ` Markus Hästbacka
2003-11-21  6:20       ` Nick Piggin
2003-11-21  9:06         ` Markus Hästbacka
2003-11-21  9:14           ` Nick Piggin
2003-11-21  9:32             ` Markus Hästbacka
2003-11-21  9:54               ` Måns Rullgård
2003-11-21 10:21                 ` Markus Hästbacka
2003-11-21 16:19                   ` Timothy Miller
2003-11-21 17:00                     ` Markus Hästbacka
2003-11-24  7:45                       ` Peter C. Ndikuwera
2004-01-12 19:40                     ` Bug found (Was: Re: Nick's scheduler v19a) Markus Hästbacka
2003-12-03 16:14             ` Nick's scheduler v19a Markus Hästbacka
2003-12-03 22:15               ` Nick Piggin
2003-12-07 21:52                 ` Markus Hästbacka
2003-12-07 23:05                   ` Nick Piggin
     [not found] <3FF79C54.4070200@cyberone.com.au>
2004-02-02 11:21 ` Markus Hästbacka

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=3FB62608.4010708@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --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