Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool2.mu.edu!uunet!easy!lron
From: lron@easy.hiam (Dwight Hubbard)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...)
Message-ID: <188dfb7a.ARN0ade@easy.hiam>
Date: 20 Jan 91 23:48:58 GMT
References: <1991Jan18.231330.16290@Neon.Stanford.EDU> <7553@sugar.hackercorp.com> <1991Jan21.004720.25985@ncsuvx.ncsu.edu> <12880@life.ai.mit.edu> <1991Jan21.055854.14130@rice.edu>
Reply-To: lron@easy.hiam
Followup-To: comp.sys.amiga.advocacy
Distribution: usa
Organization: You must be talking about someone else.
Lines: 19
Expires:
Keywords:

In article <1991Jan21.055854.14130@rice.edu>, Shawn Joel Dube writes:

> Seriously, I think cooperative is better. Take the following for example:
> Two task are running.  One is waiting on a keypress (via OS subroutine)
> and the other is doing some serious number-crunching.  With the Amiga, valuable
> time is being spent doing nothing (waiting for a keypress).  With co-op
> multitasking, almost all of the cpu time is spent with the number cruncher.

Ahh, the keyboard on the Amiga is interupt driven and NO time will be spent
waiting for a keypress.  The task waiting for the keypress will be WAITing
until the OS receives the keypress and puts it back on the READY que.  Since
the task is waiting it gets no CPU until a key is pressed and correct me if
I'm wrong but I believe the Mac does poll the keyboard so some CPU time is
wasted checking for keypresses even if none have arrived.
CDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD?
3 Dwight Hubbard                     3 USENET  : uunet!easy!lron             3
3 Kaneohe, Hawaii                    3 GT-Power: 029/004              (lron) 3
3                                    3 CFR     : 31:910/101 (Dwight Hubbard) 3
@DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDADDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDY