Path: utzoo!utgpu!water!watmath!clyde!burl!codas!ge-dab!steinmetz!davidsen
From: davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr)
Newsgroups: comp.unix.xenix
Subject: Re: COMPLAINTS about ISC UNIX V/386 (386/ix 1.0.4)
Message-ID: <8849@steinmetz.steinmetz.UUCP>
Date: 15 Jan 88 18:09:39 GMT
References: <751@vixie.UUCP> <8289@steinmetz.steinmetz.UUCP> <759@vixie.UUCP> <3018@hcrvax.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 25

In article <3018@hcrvax.UUCP> jim@hcrvax.UUCP (Jim Sullivan) writes:
| In article <759@vixie.UUCP> paul@vixie.UUCP (Paul Vixie Esq) writes:
| >In article <8289@steinmetz.UUCP> davidsen@crdos1.UUCP (bill davidsen) writes:
| >>BTW: does your vp/ix use 100% of the CPU when nothing else is running?
| >>It looks like the idle loop runs at low priority all the time. How about
| >>DOS as an idle daemon???
...
| According to a recent discussion with an Interactive representative,
| vp/ix does not busy wait for input or anything else when doing nothing.
	I based my question on the fact that if I gave the DOS command
and waited a minute on an empty system that a check on another console
showed that I had used 60sec of CPU. There was no notable impack on
loaded performance, but it sounded to me like a low priority wait loop
of some kind. If not, where does the CPU go? Someone please try this on
your system.
| This means that you can have multiple UNIX and DOS tasks running at
| the same time (like flight simulator and 123) and then switch between
| them (like when your boss arrives).  This is one of the enhancements that
| Interactive has done to DOS for hte vp/ix environment.


-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me