Messages in this thread | | | Date | Fri, 07 Jul 2000 13:26:29 +1000 | From | Andrew Morton <> | Subject | Re: [PATCH] Minor timer.c cleanup test3-pre2 |
| |
Rusty Russell wrote: > > > 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).
Where does the requirement for sync_timers() appear? How would it be used?
It's a pretty meaningless function unless called under __global_cli(), or with timerlist_lock or global_bh_lock held. Unless you're doing something fancy, which I suspect is the case...
- 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/
| |