> the soft timers really depend on a lightweight path between the
> trigger that initiates the check (e.g. return from system call)
> and the check that (usually) finds that nothing needs to be done.
BHs present exactly this path.
> a good event source for TBF.
8) TBF and CBQ in 2.2 use all the available on networked box events
and, hence, perfect softtimer approach. It fails exactly when no events
different of timer are present. Unfortunately, it is common situation.
Alexey
-
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/