home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.misc:27733 comp.os.os2.programmer:4324
- Path: sparky!uunet!kithrup!stanford.edu!ames!sun-barr!cs.utexas.edu!wupost!darwin.sura.net!jvnc.net!netnews.upenn.edu!dsinc!bagate!cbmvax!cbmehq!cbmger!edohwg!heinz
- From: heinz@edohwg.UUCP (Heinz Wrobel)
- Newsgroups: comp.os.os2.misc,comp.os.os2.programmer
- Subject: Re: Request for info about kernel pre-emption and priorities
- Message-ID: <heinz.031g@edohwg.UUCP>
- Date: 18 Aug 92 20:59:49 GMT
- References: <1992Aug13.221616.7894@ttinews.tti.com> <1992Aug14.054245.25657@nuscc.nus.sg> <19920814.005557.382@almaden.ibm.com> <mg.713847158@elan>
- Organization: Edotronik GmbH
- Lines: 25
-
- In article <mg.713847158@elan> mg@elan (Michael Golan) writes:
- >So:
- >* No magic, no 'multi threaded kernel' nor 'preemptinve kernel',
- > which are weird (and I think expensive. Anyone know of a commercial
- > widely used system designed that way?)
-
- Look at EXEC of the Amiga OS. You might consider it the Amiga's kernel.
- Preemptive multitasking is not just for your tasks there but for all of the
- OS. Single threading is done only if absolutely necessary to protect shared
- resources. So it's reentrant as far as possible. Put another way: The OS
- run's like a direct extension of your task frame, which is based on
- preemptive multitasking. Unless told otherwise the OS happily switches
- between OS calls and your SW running without any problems.
-
- But of course all this depends on how you _exactly_ define "kernel"
-
- >-- Michael Golan
-
- --
- Heinz Wrobel, Edotronik GmbH (ECG018)
- FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
- Path: cbmehq!cbmger!edohwg!heinz@cbmvax.commodore.com
- "It's good to have a mouse, it's faster if you can do without one..."
- "He who doesn't develop with an A2024 doesn't know about font independent
- user interfaces..."
-