Process scheduling.

Colin L. Hildinger (
Mon, 09 Jun 97 01:30:50 -0500

I've been gone for about 2 weeks and have returned. For you OS/2'ers
out there, I'm going to weed through the folder of stats I've
collected. I found the nice discussion interesting. In OS/2, if I run
a processor intensive task, say Quake ;-), and check back with deschall
4 hours later, nothing has happened. I mean nothing, because it's set
to idle priority. I figured nice -19 or whatever would do the same
thing on Unix, but I'm unimpressed that it doesn't on many systems.

I like OS/2's method, personally. There are four brackets of priority,
each with higher importance. A critical priority always takes
precedence over an idle one. Period. If a critical priority thread is
due, a server level one and below waits, if an server level thread is
due, an application level and below waits, and if an application level
thread is due, idle waits (I might not have gotten the names right).
There are then 32 levels of priority within each process type that
share processor time based on a fairness algorhythm.

BTW - how does it work in NT? I use it but I have to admit I'm not
intimately familiar with the scheduling. Same question for 95 I guess,
but whatever 95 does, it's poorly implemented based on the useability
of the system when you get a few processes going, especially DOS
programs. 95 can't deal with them to save its neck.

Colin L. Hildinger

Games Editor - OS/2 e-Zine!

The Ultimate OS/2 Gaming Page

The Official Unofficial AWE32 and OS/2 Warp Page