Lines Matching +full:one +full:- +full:timer +full:- +full:only

60 .Bd -literal
182 Callouts only provide a single-shot mode.
183 If a consumer requires a periodic timer,
210 .Dq multi-processor safe ;
239 A sleepable read-mostly lock
261 .Bl -tag -width ".Dv CALLOUT_RETURNUNLOCKED"
267 The lock is only acquired in read mode when running the callout handler.
279 returns a value of one.
282 negative one is returned.
320 These functions return a value of one if a pending callout was cancelled
340 Non-positive values of
363 A non-zero value for
366 other into fewer timer interrupts,
374 .Bl -tag -width ".Dv C_DIRECT_EXEC"
389 Callout functions run in this context may use only spin mutexes for locking
393 divided by acceptable time deviation: 1 -- 1/2, 2 -- 1/4, etc.
399 allow the callout subsystem to aggregate more events in one timer interrupt.
414 which uses the user-supplied
438 as its only argument.
446 Note that one of the
452 before one of the
488 loader tunable to a non-zero value.
492 loader tunable to a non-zero value.
539 function may be used to pre-calculate the absolute time at which the
563 to avoid incorrect re-adjustment.
584 .Bl -enum -offset indent
601 or one of the
634 .Bd -literal -offset indent
635 if (sc->sc_flags & SCFLG_CALLOUT_RUNNING) {
636 	if (callout_stop(&sc->sc_callout)) {
637 		sc->sc_flags &= ~SCFLG_CALLOUT_RUNNING;
705 .Bd -literal -offset indent
706 mtx_lock(&sc->sc_mtx);
707 if (callout_pending(&sc->sc_callout)) {
709 	mtx_unlock(&sc->sc_mtx);
712 if (!callout_active(&sc->sc_callout)) {
714 	mtx_unlock(&sc->sc_mtx);
717 callout_deactivate(&sc->sc_callout);
728 .Bd -literal -offset indent
729 mtx_lock(&sc->sc_mtx);
730 callout_stop(&sc->sc_callout);
754 There is one final race condition that must be considered when a
782 function families return a value of one if the callout was pending before the new
789 functions return a value of one if the callout was still pending when it was
790 called, a zero if the callout could not be stopped and a negative one is it
808 .%T "Redesigning the BSD Callout and Timer Facilities"
819 …d Hierarchical Timing Wheels: Data Structures for the Efficient Implementation of a Timer Facility"
847 introduced per-CPU callout wheels,
853 changed the underlying timer interrupts used to drive callouts to prefer
854 one-shot event timers instead of a periodic timer interrupt.