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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,38d01316d66d8f95 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.68.134.225 with SMTP id pn1mr1994205pbb.7.1331122214844; Wed, 07 Mar 2012 04:10:14 -0800 (PST) Path: h9ni49578pbe.0!nntp.google.com!news2.google.com!postnews.google.com!v2g2000vbx.googlegroups.com!not-for-mail From: slos Newsgroups: comp.lang.ada Subject: Re: Ada and linux real time Date: Wed, 7 Mar 2012 04:10:14 -0800 (PST) Organization: http://groups.google.com Message-ID: <3a01f684-b544-4051-985d-58aab98e832c@v2g2000vbx.googlegroups.com> References: <8kb66jddm0qb.1piup0wfaho1$.dlg@40tude.net> NNTP-Posting-Host: 193.251.73.50 Mime-Version: 1.0 X-Trace: posting.google.com 1331122214 22032 127.0.0.1 (7 Mar 2012 12:10:14 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 7 Mar 2012 12:10:14 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: v2g2000vbx.googlegroups.com; posting-host=193.251.73.50; posting-account=O3LyFwoAAACc1uh60ZcOUmAGdDmGsEcV User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2,gzip(gfe) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-03-07T04:10:14-08:00 List-Id: On 7 mar, 09:23, "Dmitry A. Kazakov" wrote: > On Tue, 6 Mar 2012 13:19:24 -0800 (PST), slos wrote: > > I have tried some code on both RT and non RT kernels but was not > > impressed by the difference. > > What kind of difference you expected to see? > > -- > Regards, > Dmitry A. Kazakovhttp://www.dmitry-kazakov.de I can't post the code from the place I am, so I will just describe it. My little test schedules a periodic task with a period of let's say 10ms. The periodic task then calls the Ada.Real_Time.Clock and measures the difference to the scheduled time. The difference is stored in an array of durations where each index correspond to an interval. Difference < 0.1 * period Difference < 0.2 * period Difference < 0.5 * period Difference < 1.0 * period etc... The purpose is to characterise the scheduling. Running the program for a while I get an image of how it behaves. Using both RT and non RT kernels give about same finding. Thousands are correct while some are clearly out of specified period. And I have not put any load on the system yet. I plan to use tools provided by OSADL to stress the system but of course it means nothing if I need some real time Ada runtime to achieve real time performance and can't get it for free. BR St=E9phane