Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!mit-eddie!uw-beaver!zephyr.ens.tek.com!uunet!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <15946@cbmvax.commodore.com>
Date: 19 Nov 90 16:20:40 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu> <15756@cbmvax.commodore.com> <90316.091455GIAMPAL@auvm.auvm.edu> <1834c248.ARN04024@adspdk.UUCP> <15887@cbmvax.commodore.com> <1837886c.ARN04072@adspdk.UUCP>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore, West Chester, PA
Lines: 24

In article <1837886c.ARN04072@adspdk.UUCP> hclausen@adspdk.UUCP writes:
>   To be exact, the change I've noticed is that the mouse pointer will
>block if the lower priority task does an OpenWindow(), until the Window is
>done. This is the (minor) change I've met. I remember from Paris that the
>Intuition state machine was completely rewritten, which is far more that
>happened to Exec. Changes to side effects can be expected and should be
>identified.

I don't know how much of OpenWindow() was done on input.device's task
under 1.3.  There is a reasonable amount of work to be done in 2.0.
We try to avoid putting too much burden on the input.device, but
it is indeed possible that more stuff uses it.  OpenWindow() doesn't
seem to do much more than locking the layer_info, and creating the
window layer.  Most of the rest happens on your schedule.

>|                       Henrik Clausen, Graffiti Data                    |
>|           ...{pyramid|rutgers}!cbmvax!cbmehq!adspdk!hclausen           |

     Peter
--
     Peter Cherna, Software Engineer, Commodore-Amiga, Inc.
     {uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
I have found a proof for Fermat's theorem, but there is no room in the .sig!