|
|
@@ -18,7 +18,7 @@
|
|
|
|
|
|
<h2 class='titleHead'>The Linux Kernel Module Programming Guide</h2>
|
|
|
<div class='author'><span class='ecrm-1200'>Peter Jay Salzman, Michael Burian, Ori Pomerantz, Bob Mottram, Jim Huang</span></div><br />
|
|
|
-<div class='date'><span class='ecrm-1200'>September 2, 2021</span></div>
|
|
|
+<div class='date'><span class='ecrm-1200'>September 3, 2021</span></div>
|
|
|
|
|
|
|
|
|
|
|
|
@@ -4475,10 +4475,10 @@ processing a more important interrupt, in which case it will deal with this one
|
|
|
when the more important one is done), saves certain parameters on the stack and
|
|
|
calls the interrupt handler. This means that certain things are not allowed in the
|
|
|
interrupt handler itself, because the system is in an unknown state. Linux kernel
|
|
|
-solves the problem by splitting interrupt handling into two parts. The first
|
|
|
-part executes right away and mask the interrupt line. Hardware interrupts
|
|
|
-must be handled quick, and that is why we need the second part to handle
|
|
|
-the heavy work deferred from a interrupt handler. Historically, BH (Linux
|
|
|
+solves the problem by splitting interrupt handling into two parts. The first part
|
|
|
+executes right away and masks the interrupt line. Hardware interrupts must be
|
|
|
+handled quickly, and that is why we need the second part to handle the
|
|
|
+heavy work deferred from an interrupt handler. Historically, BH (Linux
|
|
|
naming for <span class='ecti-1000'>Bottom Halves</span>) statistically book-keeps the deferred functions.
|
|
|
<span class='ecbx-1000'>Softirq </span>and its higher level abstraction, <span class='ecbx-1000'>Tasklet</span>, replace BH since Linux
|
|
|
2.3.
|
jserv