[okl4-developer] OKL4 and timer service.

[Jean-Christophe Dubois]

No opinion either?

JC

On Friday 28 August 2009 00:52:51 Jean-Christophe Dubois wrote:
> Hi,
>
> I am just wondering if somebody could give me some rational on the decision
> not to include a generic timer service inside OKL4.
>
> The fact is that OKL4 is capturing at least one set of timer from the
> platform preventing any Cell to access this one (which is a good thing) and
> uses it for its own internal need.
>
> Now if the platform has no more other timer to offer to the Cells, it does
> mean that the Cells will never be able to grab any timer in order to do
> some type of timeout functions. So simple function like sleep() and such
> would not be possible.
>
> Moreover, assuming you have one timer free for use, if you have multiple
> Cells in need of such services you would have to actually implement
> something like a virtual timer server to serve the need of your multiple
> Cells.
>
> Meanwhile the OKL4 kernel has its own timer with which it does its own tick
> stuff without any intention to share it.
>
> So why is it a bad thing (or at least not considered) to offer one central
> an easily accessible timer service in OKL4 lib using the OKL4 timer under
> the cover? Why is it preferable to force the user to implement its own
> virtual timer server to be used by its application (possibly composed of
> multiple cells each running a program or an OS in need of a time interrupt
> source)
>
> Thanks
>
> JC
>
>
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer