From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5bcf30769d6d9599
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-08-28 10:25:34 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.mathworks.com!nycmny1-snh1.gtei.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: ADA os talk
Date: 28 Aug 2001 12:25:31 -0500
Organization: LJK Software
Message-ID: <JRF6lDDqt9kq@eisner.encompasserve.org>
References: <mailman.998888394.11895.comp.lang.ada@ada.eu.org>
 <9mdmck$rs1$1@nh.pace.co.uk> <9me6q4$aai1@news.cis.okstate.edu>
 <MIj1nYP7aabe@eisner.encompasserve.org> <9mg7fr$rm1$1@nh.pace.co.uk>
 <3CeB8M0VaOC6@eisner.encompasserve.org> <9mgg0p$26j$1@nh.pace.co.uk>
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 999019027 17851 192.135.80.34 (28 Aug 2001
 17:17:07 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Tue, 28 Aug 2001 17:17:07 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:12528
Date: 2001-08-28T12:25:31-05:00
List-Id: <comp.lang.ada>

In article <9mgg0p$26j$1@nh.pace.co.uk>, "Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> writes:

> Like I said, my memory of the situation whas that techniques were possible
> under VMS to run realtime, but that VMS wasn't designed to specifically
> provide some kind of realtime mode. Sort of a case where if you had enough
> privileges and enough priority and could keep anything else from taking
> precidence, you could convince yourself that you had fixed latency and
> weren't going to get swapped out. This is different than having a process
> that the OS manages in realtime mode and guarantees you that none of this is
> going to fail.

Absolutely VMS is designed so that you need privilege to alter its
behavior.  By default there is fair treatment for all, and that is
certainly inadequate for realtime needs.  The controls to tweak,
however, are all documented as being "for realtime", and those of
us who pass them every day (and ignore them) tend to presume the
priority mechanisms are adequate.  The scheduling algorithm has
a different behavior in the upper half of the priority range,
for instance, specifically for realtime.