winscape 2316
the original (release 1) cp-67 scheduler (what i initially saw when they brought it out to the univ. in jan. 1968) was effectively...
That, Barb, is an interesting observation. A finer distinction than your usual compiler v OS thinking.
Dave Cutler, as far as I know was the first with $INTSAV, $DIRXT and $FORK0 in RSX11-M around 1975. That was an excellent I-O design. It has stood the test of time, and lives on in VMS and NT.
which I guess is your point. But that is well on the way to 'timesharing thinking'. The RSX round robin was not a huge piece of extra code in the exec, and, perhaps I was imagining it at the time, seemed to use a similar technique to TOPS-10, namely fooling about with the process priorities within a certain (timesharing user) range. So that real-time processes above that range could not be hurt, and for I-O to spend a tiny amount of time at elevated hardware priority.
I don't know for sure whether Dave did the round robin, but he sure as hell must have understood it. It is not *that* hard.
To relate this EXACT topic to one near and dear to Barb's heart, Tom Hastings' name appears on both the CTSS scheduler, and on the one in CLKCSS.MAC...
Or am I missing some other ingredient of 'timesharing thinking'? I'm genuinely interested. I might be stuck too far into 'task-based' myself to see the wood for the trees.
-- To de-mung my e-mail address:- fsnospam$elliott$$ PGP Fingerprint: 1A96 3CF7 637F 896B C810 E199 7E5C A9E4 8E59 E248