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,38d01316d66d8f95 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.232.169 with SMTP id tp9mr9191377pbc.6.1332162156653; Mon, 19 Mar 2012 06:02:36 -0700 (PDT) Path: kz5ni6130pbc.0!nntp.google.com!news1.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Ada and linux real time Date: Mon, 19 Mar 2012 13:01:22 +0000 Organization: A noiseless patient Spider Message-ID: References: <8kb66jddm0qb.1piup0wfaho1$.dlg@40tude.net> <3a01f684-b544-4051-985d-58aab98e832c@v2g2000vbx.googlegroups.com> <13z45jd9irz9x.1j2hj7ayxwkyj.dlg@40tude.net> <5777a4dc-67ef-4a35-b929-653a4d498aac@q11g2000vbu.googlegroups.com> <4f67187d$0$7625$9b4e6d93@newsspool1.arcor-online.net> Mime-Version: 1.0 Injection-Info: mx04.eternal-september.org; posting-host="dFCm8HWntFqmDIilBLqEJQ"; logging-data="11323"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX183eC/vRAe1ls6qsMxBFbqr6zWVI76W1lI=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin) Cancel-Lock: sha1:E3Uj8PCvtSLjhBIqCy6qReLldYM= sha1:a7cbm0lIayZ7grAMGA4/SoepHug= Content-Type: text/plain; charset=us-ascii Date: 2012-03-19T13:01:22+00:00 List-Id: Georg Bauhaus writes: > On 18.03.12 23:03, slos wrote: > >> delay until Next_Time; >> >> MyDuration := To_Duration (Clock - Next_Time); > > I haven't looked very closely, but if, say, Next_Time has a value of > 12 o'clock, then > > delay until Next_Time; > > -- (it is now 12 o'clock) > > My_Duration := Clock - Next_Time; > > will likely measure 12 o'clock - 12 o'clock, unless performing "-" > takes time, or (parts of) the assignment statement is (are) put on > hold by the scheduler, interrupting the task. I think that's unlike > Simon's program, which subtracts a starting time, not next_time, from > the current time. I think the point of slos's code is that the delay is supposed to finish at Next_Time, but may (if the OS isn't very 'RT') finish later; the code measures this. I tried this on the same machine as my last report, but got the same result using 'chrt 1 ./rt_test' as plain './rt_test' (running grep -r 'an unlikely phrase' . in another window).