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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,cae92f92d6a1d4b1 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!goblin2!goblin.stu.neva.ru!news.internetdienste.de!noris.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Ada.Execution_Time Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <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> <1akm5muxu9zni.mu91b7pubqw0$.dlg@40tude.net> <8nrg25FoucU1@mid.individual.net> <2k07hwmh6123.1pgx57welw9of$.dlg@40tude.net> <8nsa76Fj4rU1@mid.individual.net> <1j9i6trxinqtg$.renlw9wdtpsf.dlg@40tude.net> <4kkxaiynm22p$.sld84rm8849d$.dlg@40tude.net> Date: Tue, 28 Dec 2010 17:34:06 +0100 Message-ID: NNTP-Posting-Date: 28 Dec 2010 17:34:07 CET NNTP-Posting-Host: d4fe5d25.newsspool2.arcor-online.net X-Trace: DXC=_P]]`IHCFTjOKO]LCQ@0g`A9EHlD;3Ycb4Fo<]lROoRa8kF On Tue, 28 Dec 2010 16:18:11 +0000, Simon Wright wrote: > "Dmitry A. Kazakov" writes: > >> Yes, this thing. In our case it was Pentium VxWorks 6.x. (The PPC we >> used prior to it had poor performance) The problem was that >> Ada.Real_Time.Clock had the accuracy of the clock interrupts, >> i.e. 1ms, which is by all accounts catastrophic for a 1.7GHz >> processor. You can switch some tasks forth and back between two clock >> changes. > > Our experience was that where there are timing constraints to be met, or > cyclic timing behaviours to implement, a milliscond is OK. > > We did consider running the VxWorks tick at 100 us but this was quite > unnecessary! We actually have it set at 100 us, I believe. But we need high accuracy clock not for switching tasks. It is for time stamping and frequency measurements. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de