Re: Faster timers for Linux 2.1.22

Alan Cox (
Mon, 27 Jan 1997 09:54:26 +0000 (GMT)

> As for 'buffering', after disable_bh is called, the next interrupt of
> any kind including (AFAIK) the timer tick will run any outstanding
> bottom half code. This takes precedence over user driven code. It's a
> tradeoff, a more local lock and a slightly delayed bh against a global
> lock that hits every piece of code.

Thats too expensive for networking and for other things. However what
Ingo suggested which is having an enable_bh() or variant that does run
pending bh handlers solves it