Return-Path: <[log in to unmask]>
Received: from minnow.catalina-inter.net ([207.105.234.21])
          by skipper.catalina-inter.net (post.office MTA v2.0 0813
          ID# 0-14005) with ESMTP id AAA338 for <[log in to unmask]>;
          Wed, 28 Oct 1998 13:57:19 -0800
Received: from dawn.bna.boeing.com (dawn.cal.boeing.com [129.172.51.52])
        by minnow.catalina-inter.net (8.8.7/8.8.7) with ESMTP id NAA10191
        for <[log in to unmask]>; Wed, 28 Oct 1998 13:57:18 -0800
Received: from slopok.roses.bna.boeing.com ([141.102.33.160])
        by dawn.bna.boeing.com (8.8.5/8.8.5) with ESMTP id NAA12744;
        Wed, 28 Oct 1998 13:49:54 -0800 (PST)
Received: from catalina-inter.net (redmax [141.102.60.228])
        by slopok.roses.bna.boeing.com (8.8.7/8.8.7) with ESMTP id NAA04438;
        Wed, 28 Oct 1998 13:57:27 -0800 (PST)
Sender: [log in to unmask]
Message-ID: <[log in to unmask]>
Date: Wed, 28 Oct 1998 13:57:27 -0800
From: Chris Sparks <[log in to unmask]>
X-Mailer: Mozilla 4.07 [en] (X11; U; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: gnat chat <[log in to unmask]>
Subject: Timer resolution
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

Has anyone done any timing studies of Ada.Real_Time on Linux?  In
particular
how accurate (to what millisecond) is it.  I am trying to run a small
Ada
kernel (aka process management software) on Linux that was once on an
embedded system.  On the embedded system the time was triggered from an
interrupt.  Not going to get that kind of control on Linux.  I resorted
to
using "delay until" and "clock".  It seems that the resolution of the
clock's
firing is not in sync with the actual clock time.  In other words I
assume
a 100 millisecond interrupt time and get 10 milliseconds between
intervals.
I tried a 10 millisecond interrupt time and got 1 second between
intervals.
Something is wrong here.

Thanks,
Chris Sparks