linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wes Janzen <superchkn@sbcglobal.net>
To: Con Kolivas <kernel@kolivas.org>
Cc: Ian Kumlien <pomac@vapor.com>,
	Daniel Phillips <phillips@arcor.de>,
	linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net>
Subject: Re: [SHED] Questions.
Date: Tue, 02 Sep 2003 05:44:36 -0500	[thread overview]
Message-ID: <3F547494.6080205@sbcglobal.net> (raw)
In-Reply-To: <200309021023.24763.kernel@kolivas.org>

Con Kolivas wrote:

> ...
>
>The cpu scheduler simply isn't broken as the people on this mailing list seem 
>to think it is. While my tweaks _look_ large, they're really just tweaking 
>the way the numbers feed back into a basically unchanged design.
>
>...
>

For what it's worth, I haven't had any problems with Con's O19int.  I've 
been trying to repeat a case of priority inversion I experienced with 
O18.1...but it seems to be cured (and that was really my only problem 
with it).  I was already getting fewer skips in XMMS with 
2.6.0-test3-mm2 than I did with 2.4.18 and the same sort of workload.  I 
can't really test xmms now that the ACPI changes have obliterated my 
chances of freeing IRQ 5 for my sb16 -- but from the improvements I feel 
in the last few patches from Con, I imagine that it wouldn't skip 
anymore.  (On a side note, I really miss xmms where random means quite 
random, unlike my CD changer which is repeat the same songs in a four 
hour block.)  I certainly am not running any sort of high-end machine 
with a K6-2 400 ;-)  The mouse might lag slightly for a few seconds when 
starting up a build, but as soon as the scheduler adjusts, I can't tell 
whether I have four builds running at the same time or just one.  In 
2.4.18, it has a slow feeling that let's you know the system is loaded 
-- and it never goes away (well, until the compiling's done).

-Wes-


      parent reply	other threads:[~2003-09-02 10:42 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
2003-09-03 23:02                         ` Ian Kumlien
2003-09-04  1:39                           ` Mike Fedyk
2003-09-02 10:44                 ` Wes Janzen [this message]

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=3F547494.6080205@sbcglobal.net \
    --to=superchkn@sbcglobal.net \
    --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).