Load control and intelligence in schedulers

[Tim Smith]

In article <161 at desint.UUCP> ...!ihnp4!trwrb!desint!geoff (Geoff Kuenning) says:
>
>Programs that try to outsmart schedulers can be a serious problem.
>But I wasn't talking about rewarding terminal output.  It is terminal
>*input* that drives user's perceptions of response times, and thus
>that is the only way to get a big priority kick.  Naturally, nobody
>wants to 'babysit' a compute-bound program by giving it a CR every
>second or so to keep it going (especially since a proper
>implementation would ensure that only blocking reads gave the
>priority boost).

Isn't this what auto-repeat and chewing gum are for?
-- 
					Tim Smith
			ihnp4!wlbr!callan!tim or ihnp4!cithep!tim