next up previous contents
Next: Task Queues Up: Kernel Mechanisms Previous: Kernel Mechanisms

Bottom Half Handling


Figure: Bottom Half Handling Data Structures

There are often times in a kernel when you do not want to do work at this moment. A good example of this is during interrupt processing. When the interrupt was asserted, the processor stopped what it was doing and the operating system delivered the interrupt to the appropriate device driver. Device drivers should not spend too much time handling interrupts as, during this time, nothing else in the system can run. There is often some work that could just as well be done later on. Linux's bottom half handlers were invented so that device drivers and other parts of the Linux kernel could queue work to be done later on. Figure gif shows the kernel data structures associated with bottom half handling.

There can be up to 32 different bottom half handlers; bh_base  is a vector of pointers to each of the kernel's bottom half handling routines. bh_active  and bh_mask  have their bits set according to what handlers have been installed and are active. If bit N of bh_mask  is set then the Nth element of bh_base  contains the address of a bottom half routine. If bit N of bh_active  is set then the N'th bottom half handler routine should be called as soon as the scheduler deems reasonable. These indices are statically defined; the timer bottom half handler is the highest priority (index 0), the console bottom half handler is next in priority (index 1) and so on. Typically the bottom half handling routines have lists of tasks associated with them. For example, the immediate bottom half handler works its way through the immediate tasks queue (tq_immediate ) which contains tasks that need to be performed immediately.

Some of the kernel's bottom half handers are device specific, but others are more generic:

This handler is marked as active each time the system's periodic timer interrupts and is used to drive the kernel's timer queue mechanisms,
This handler is used to process console messages,
This handler is used to process tty messages,
This handler handles general network processing,
This is a generic handler used by several device drivers to queue work to be done later.

Whenever a device driver, or some other part of the kernel, needs to schedule work to be done later, it adds work to the appropriate system queue, for example the timer queue and then signals the kernel that some bottom half handling needs to be done. It does this by setting the appropriate bit in bh_active . Bit 8 is set if the driver has queued something on the immediate queue and wishes the immediate bottom half handler to run and process it. At the end of each time a system call a check is made on bh_active  to see if it has any bits set. If it has, the bottom half handler routines that are active are called. Bit 0 is checked first, then 1 and so on until bit 31.

The bit in bh_active  is cleared as each bottom half handling routine is called. bh_active  is transient; it only has meaning between calls to the scheduler and is a way of not calling bottom half handling routines when there is no work for them to do.

next up previous contents
Next: Task Queues Up: Kernel Mechanisms Previous: Kernel Mechanisms

David A. Rusling