home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.misc:27294 comp.os.os2.programmer:4199
- Newsgroups: comp.os.os2.misc,comp.os.os2.programmer
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!jvnc.net!nuscc!eletanjm
- From: eletanjm@nuscc.nus.sg (TAN JIN MENG)
- Subject: Re: Request for info about kernel pre-emption and priorities
- Message-ID: <1992Aug13.155927.6849@nuscc.nus.sg>
- Organization: National University of Singapore
- References: <1992Aug12.163357.34974@ans.net>
- Date: Thu, 13 Aug 1992 15:59:27 GMT
- Lines: 16
-
- db3l@ans.net (David Bolen) writes:
- :
- : In OS/2 1.x, I believe the time latency from when a high priority thread
- : became "ready to run" (either resource released, or the thread was unblocked
- : due to some other mechanism, such as a timer firing) until it got control of
- : the CPU was guaranteed to be <1ms. Not the greatest in terms of real-time
- : operation, but not bad for a multitasking OS. I'm not how much, if at all,
- : that figure has been adjusted for v2.0.
-
- I have measured the average context switch time and the average time
- for a high priority thread to preempt a low priority thread to be
- 84 usecs and 250 usecs (about - I'm doing this from home so I can't
- verify again - my memory got holes) on OS/2 2.0 with WPS loaded on a
- 486-33DX AT clone.
-
- jin meng
-