Re: delay until and GNAT - expand

[rracine@draper.com (Roger Racine)]

In article <7h9nal$9dr$1@nnrp1.deja.com> Robert Dewar <robert_dewar@my-dejanews.com> writes:
>In article <7h9j77$61l$1@nnrp1.deja.com>,
>  dennison@telepath.com wrote:
>> What I am seeing is that "interrupt 0", the clock interrupt,
>takes about
>> 11 micro seconds. Then the slighly misnamed "idle" task
>continues to
>> execute for about 11 micros. Then my Ada task begins. Where in
>there my
>> Ada code starts executing again rather than vxWorks system
>calls, I
>> cannot tell with Windview. But all totaled that is about 22
>microseconds
>> from the clock tick at which the delay expired to the time my
>Ada task's
>> context was switched to.

>20 microseconds sounds much more in the region that I would
>expect than Roger's one microsecond.

>Robert Dewar

We are obviously talking about different metrics.  The original message (as 
expanded) asked about the "delay 0.0" case, not a positive value.  So your 
clock interrupt goes away, as does the idle task execution (which is all of 
your measured time).

All that is needed (not necessarily all that is done) is a check for positive, 
and, if not, a call to "sched_yield" (POSIX interface), which puts the task at 
the end of the ready queue and performs a context switch.

Let's make sure we are all measuring the same thing.

Roger Racine