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-Thread: a07f3367d7,cae92f92d6a1d4b1 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Ada.Execution_Time Date: Sat, 01 Jan 2011 15:54:19 +0000 Organization: A noiseless patient Spider Message-ID: References: <4d05e737$0$6980$9b4e6d93@newsspool4.arcor-online.net> <1wmsukf0wglz3$.odnzonrpayly.dlg@40tude.net> <6n1c5myuf2uz$.10jl3ln7il3aq.dlg@40tude.net> <8n0mgnFv2sU1@mid.individual.net> <1n3o55xjdjr9t.1u33kb75y2jfl$.dlg@40tude.net> <8n1142Fto2U1@mid.individual.net> <1o5cbm4b1l20d$.19winbma6k5qw.dlg@40tude.net> <8n4mskF7mmU1@mid.individual.net> <8nm30fF7r9U1@mid.individual.net> <8o0p0lF94rU1@mid.individual.net> <8o4k3tFko2U1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="dFCm8HWntFqmDIilBLqEJQ"; logging-data="8806"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+wUCBElG8a/1jqp7LqLT+rD8Xw2cnsgb0=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin) Cancel-Lock: sha1:2Rox1JcbrSpR/8AGIf5G35EFLvk= sha1:Y/sp91wRP2/HX6XKli7tL0Ji2c0= Xref: g2news2.google.com comp.lang.ada:17265 Date: 2011-01-01T15:54:19+00:00 List-Id: "Randy Brukardt" writes: > Your discussion of real-time scheduling using this still seems to me > to be more in the realm of academic exercise than something > practical. I'm sure that it works in very limited circumstances, but > those circumstances are getting less and less likely by the year. Sounds as if you don't agree with the !problem section of AI-00307? The first paragraph says that measurement/estimation is important, and that measurement is difficult [actually, I don't see this; _estimation_ is hard, sure, what with pipelining, caches etc, but _measurement_?] The second paragraph says that in a hard real time system you ought to be able to monitor execution times in order to tell whether things have gone wrong. Hence Ada.Execution_Time.Timers. The third paragraph talks about fancy scheduling algorithms. This is the point at which I too start to wonder whether things are getting a bit academic; but I have no practical experience of the sort of real-time systems under discussion. We merely have to produce the required output within 2 ms of a program interrupt; but the world won't end if we miss occasionally (not that we ever do), because of the rest of the system design, which has to cope with data loss over noisy radio channels. The last paragraphs call up the Real-Time extensions to POSIX (IEEE 1003.1d, after a lot of googling) as an indication of the intention.