Why RTEMS timeslice is not as configured.

Wendell Silva silvawp at gmail.com
Mon Jul 8 22:30:18 UTC 2013


Is this 'time dilatation' linear?
I mean, if you configure shorter/bigger timeslices the factor of
'dilatation' is the same?

--Wendell


2013/7/8 Fernando Nicodemos <fgnicodemos at ncb.ind.br>

> Dears,
>
> I configured 4 equal Tasks in RTEMS and the table as follows:
>
> rtems_task_create(
> Task_name[ 0 ],
> 2,
> RTEMS_MINIMUM_STACK_SIZE * 2,
> RTEMS_PREEMPT | RTEMS_TIMESLICE | RTEMS_ASR | RTEMS_INTERRUPT_LEVEL(0),
> RTEMS_GLOBAL,
> &Task_id[ 0 ]
> );
>
> They will operate in round-robin.
>
> #define CONFIGURE_MICROSECONDS_PER_TICK 10000
> #define CONFIGURE_TICKS_PER_TIME_SLICE 50
>
> The result should show a timeslice of 500 milisseconds, but what i see in
> osciloscope is more then 500ms, exactly 834ms. This code is running in a
> ERC32 development kit from Atmel.
>
> Any ideas what is missing for this extra time?
>
> Thanks,
>
> *Fernando G. Nicodemos*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130708/8b1576f5/attachment-0001.html>


More information about the users mailing list