Product Focus – First Source for Red-Hot Linux 2.6 Drivers

If you have been using Linux, you are aware of the slow interrupt response inherent in version 2.4. In fact, an active debate about the causes of the sluggishness and possible fixes continued in the Linux community throughout the three years between the releases of Linux 2.4 and 2.6. For many 2.4 users, proprietary patches had to be used to address scheduler latency.

Actually, there are four elements that contribute to the overall delay between an interrupt and the time the associated application program starts to run: interrupt latency, interrupt handler duration, scheduler latency, and scheduling duration. Of these, scheduler latency was by far the largest.

In the 2.4 kernel, the process scheduler could not run when a process was executing in a system call. This restriction explains the 232-ms maximum latency measured in one test that also found a mean latency value of
88 's.¹ In the same test,
so-called low-latency patches were inserted that added explicit preemption points to allow very long routines to be interrupted if the scheduler needed to run. These patches reduced the mean latency to about 54 's but limited the maximum latency to only 1.3 ms.

A second approach was to interrupt the executing process if possible. Although the Linux kernel was not originally written to support preemptive interrupts, they had become practical by 2.4, and an appropriate set of patches could be added.

Linux 2.6 incorporates these changes as well as important modifications to the process scheduler and the way in which resources are shared among competing threads. The effect of these and other alterations is to save time. In a test of the new kernel, a 500-MB file was read in
3.9 s vs. 37 s for the 2.4 kernel.² In this case, much of the improvement was due to a new anticipatory I/O scheduler that avoids unnecessary process queuing.

In UEI's investigations of the performance of a PowerDAQ MF multifunction card, a benchmark program was run under Linux 2.6 on a 1-GHz Pentium III with 256 MB of memory. When an interrupt was received in the low-level driver, the test read the processor time-stamp counter (TSC). When the user program received the event corresponding to the interrupt, the TSC was read again and the two values subtracted to determine the overall latency.

Although increased interrupt handling speed is the feature key to high-speed operation of the UEI cards, Linux 2.6 doesn t stop there. In multiprocessing applications, it handles 64 processors vs. 16 for 2.4 and can address 4,095 devices compared to 255. The memory space also increases from 16 GB to 64 GB of RAM and from 2 TB to 16 TB for file systems.

These new capabilities may not be as important to data acquisition as they are to enterprise applications attempting to challenge UNIX.² However, by addressing all of 2.4's deficiencies, the new 2.6 kernel ensures continued Linux growth. That can t be a bad thing for designers deciding what operating system to use for their next project.

www.rsleads.com/404ee-199

References