I have some thoughts and questions about timer implementation in
linux-generic.
Current implementation:
sigev.sigev_notify = SIGEV_THREAD;
sigev.sigev_notify_function = timer_notify;
sigev.sigev_value.sival_ptr = tp;
timer_create(CLOCK_MONOTONIC, &sigev, &tp->timerid);
t
On Thu, Jan 28, 2016 at 09:31:52PM +0300, Maxim Uvarov wrote:
> I have some thoughts and questions about timer implementation in
> linux-generic.
>
> Current implementation:
>
> sigev.sigev_notify = SIGEV_THREAD;
> sigev.sigev_notify_function = timer_notify;
> sigev.sigev_val
This is how you implement timers in HW as well. A separate HW block
operates a scan loop that constantly searches for timers to expire and
creates events for those who do. The rest of the system operates
undisturbed. For a SW analog in manycore systems you'd have service
thread(s) running on ded
On 28.01.16 20:31, Maxim Uvarov wrote:
I have some thoughts and questions about timer implementation in linux-generic.
Current implementation:
sigev.sigev_notify = SIGEV_THREAD;
sigev.sigev_notify_function = timer_notify;
sigev.sigev_value.sival_ptr = tp;
timer_cre
On 28.01.16 20:31, Maxim Uvarov wrote:
I have some thoughts and questions about timer implementation in linux-generic.
Current implementation:
sigev.sigev_notify = SIGEV_THREAD;
sigev.sigev_notify_function = timer_notify;
sigev.sigev_value.sival_ptr = tp;
timer_cre
On 29.01.16 00:54, Bill Fischofer wrote:
This is how you implement timers in HW as well.
A separate HW block operates a scan loop that constantly searches for timers to
expire and creates events for those who do.
The rest of the system operates undisturbed. For a SW analog in manycore
syste
On 29 January 2016 at 05:16, Ivan Khoronzhuk
wrote:
>
>
> On 29.01.16 00:54, Bill Fischofer wrote:
>
>> This is how you implement timers in HW as well.
>>
> A separate HW block operates a scan loop that constantly searches for
> timers to expire and creates events for those who do.
> The rest of
