From: George Anzinger <george@mvista.com>
To: rob@landley.net
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Ingo Molnar and Con Kolivas 2.6 scheduler patches
Date: Thu, 14 Aug 2003 01:01:11 -0700 [thread overview]
Message-ID: <3F3B41C7.1000906@mvista.com> (raw)
In-Reply-To: <200308132024.36967.rob@landley.net>
Rob Landley wrote:
> On Saturday 09 August 2003 16:52, George Anzinger wrote:
>
>>Ed Sweetman wrote:
>>
>>>the problem is you want a process that works like it was run on a single
>>>tasking OS on an operating system that is built from the ground up to be
>>> a multi-user multi-tasking OS
>
>
> Considering the multi-tasking OS has 1000 times the CPU power, memory, and
> disk space as the single-tasking OS did when it debuted, yet still loses to
> it in some areas, isn't it at least worth looking at?
>
>
>>>and you want both to work perfectly at peak performance
>
>
> We're pondering various heuristics with which to to improve the situation and
> you say we're persuing perfection. From heuristics.
>
> Do you say these sort of things to the virtual memory people? (Since you
> can't do it perfectly, why bother to swap at all? The perfect being the
> enemy of the good, and all that.)
>
>
>>>and you want it to know when you want which to work at
>>>peak performance automatically.
>
>
> I know for a fact that automatic determination of interactivity is possible.
> In OS/2 you could speed up a compile by moving the mouse pointer over its
> window repeatedly to give it extra clock ticks. (So far we've managed to
> avoid anything quite so disgusting in Linux, but there exist OSes where it
> was done. Having the keyboard and mouse and display be local devices is
> actually the common case. It took X about ten years to finally start
> optimizing for the common case on the output side with MIT shared memory
> extensions and such...)
>
> The scheduler actually has a lot of information to work with. Ingo's patches
> strive to give it more information, and and Con's patches make much better
> use of that information. This is a good thing.
>
>
>>Well said :)
>
>
> Actually, I didn't really consider that list of straw man arguments to be
> worth commenting on the first time around. (I thought he was being
> sarcastic...)
Well, I think he was too, but I am trying to say (as I think you are
too) that it is not far from being a realistic goal.
As to timing, I just changed ISPs and was off line for a few days...
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-08-14 8:01 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 9:30 Ingo Molnar and Con Kolivas 2.6 scheduler patches Felipe Alfaro Solana
2003-07-26 9:46 ` Marc-Christian Petersen
2003-07-26 10:02 ` Ismael Valladolid Torres
2003-07-26 10:10 ` Eugene Teo
2003-07-26 11:24 ` Ed Sweetman
2003-07-26 17:00 ` Rahul Karnik
2003-07-27 15:46 ` Daniel Phillips
2003-07-26 16:52 ` Diego Calleja García
2003-07-26 18:35 ` Andrew Morton
2003-07-26 23:01 ` Diego Calleja García
2003-07-28 9:38 ` Felipe Alfaro Solana
2003-07-28 10:37 ` Måns Rullgård
2003-07-28 17:06 ` Diego Calleja García
2003-07-27 2:38 ` Con Kolivas
2003-07-27 7:39 ` Willy Tarreau
2003-07-27 9:12 ` Ingo Molnar
2003-07-27 11:54 ` Con Kolivas
2003-07-27 20:18 ` Daniel Phillips
2003-07-26 22:05 ` Ed Sweetman
2003-08-01 15:38 ` Daniel Phillips
2003-07-31 23:02 ` Ed Sweetman
2003-07-27 2:39 ` Ed Sweetman
2003-07-29 13:56 ` Timothy Miller
2003-07-29 13:57 ` Con Kolivas
2003-07-29 15:30 ` Timothy Miller
2003-07-29 15:52 ` Helge Hafting
2003-07-29 16:26 ` Timothy Miller
2003-07-30 14:46 ` Daniel Phillips
2003-07-29 15:40 ` Timothy Miller
2003-07-30 16:17 ` Daniel Phillips
2003-08-08 21:09 ` Bill Huey
2003-08-06 21:28 ` Rob Landley
2003-08-07 9:34 ` Helge Hafting
2003-08-07 15:42 ` Daniel Phillips
2003-08-07 20:45 ` William Lee Irwin III
2003-08-07 20:51 ` Rob Landley
2003-08-07 21:40 ` Ed Sweetman
2003-08-07 22:17 ` William Lee Irwin III
2003-08-08 0:01 ` Rob Landley
2003-08-09 20:52 ` George Anzinger
2003-08-14 0:24 ` Rob Landley
2003-08-14 8:01 ` George Anzinger [this message]
2003-08-16 9:10 ` Rob Landley
2003-08-16 14:29 ` APM and 2.5.75 not resuming properly Jamie Lokier
2003-08-16 15:03 ` Stephen Rothwell
2003-08-16 16:12 ` Jamie Lokier
2003-08-16 20:43 ` Rob Landley
2003-08-13 3:38 ` Ingo Molnar and Con Kolivas 2.6 scheduler patches George Anzinger
2003-08-08 6:08 ` Daniel Phillips
2003-07-26 12:08 ` Ismael Valladolid Torres
2003-07-26 14:54 ` Con Kolivas
2003-07-26 14:49 ` Con Kolivas
2003-07-26 14:47 ` Con Kolivas
2003-07-26 16:42 ` Lou Langholtz
2003-07-26 16:40 ` Jens Axboe
2003-07-26 18:19 ` William Lee Irwin III
2003-07-26 18:31 ` Felipe Alfaro Solana
2003-07-26 19:20 ` William Lee Irwin III
2003-07-26 19:47 ` William Lee Irwin III
2003-07-27 9:24 ` Ingo Molnar
2003-07-27 9:57 ` Con Kolivas
2003-07-27 10:02 ` Ingo Molnar
2003-07-27 10:19 ` Con Kolivas
2003-07-28 22:44 ` Timothy Miller
-- strict thread matches above, loose matches on Subject: below --
2003-07-26 14:44 Downing, Thomas
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=3F3B41C7.1000906@mvista.com \
--to=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.