> More hmm... synchronize_bh() doesn't do anything to stop a new BH from
> starting as soon as it has returned. So it's safe within __global_cli()
> and it can be used after del_timer() to give del_timer_sync() semantics,
> but apart from that, what use is it??
Im thinking
del_timer();
del_timer();
blah
wait_timers();
Which happens to avoid the overhead and cost in the normal timer deletion
path.
> BTW2: is there any technical reason why the timer_struct clients haven't
> been migrated over to use timer_list yet?
Not that I know of
-
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 : Thu May 25 2000 - 10:26:50 EDT