In message <3962A854.62A316@uow.edu.au> you write:
> Agree. We should also not export timer_synchronize(), as it is only
> useful/meaningful/safe when used under timerlist_lock, or when used on a
> non-reinstalling timer. The subtleties of this probably mean that if
> someone tried to use timer_synchronize() they'd get it wrong :( I'd
> like to see the following interface:
>
> del_timer_async() -> delete a timer, may still be running
> del_timer_sync() -> delete a timer, may deadlock
> del_timer() -> Legacy, deprecated async deletion
>
> and _nothing_ else.
Yep, plus:
sync_timers() -> finish all timers currently running (this can be
trivially implemented as spin_lock_wait(&global_bh_lock).
Rusty.
-- Hacking time.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:20 EST