deploy: 29504e922916cca1f405ea1a78e5c419fbe63547

This commit is contained in:
jserv 2025-04-12 05:11:22 +00:00
parent a135017dd1
commit 9e32b6e0af
2 changed files with 6 additions and 6 deletions

View File

@ -5392,9 +5392,9 @@ interrupts, is much harder to implement because it has to be dealt with when
convenient for the hardware, not the CPU. Hardware devices typically have a very
small amount of RAM, and if you do not read their information when available, it is
lost.
</p><!-- l. 1954 --><p class='indent'> Under Linux, hardware interrupts are called IRQs (Interrupt ReQuests). There
are two types of IRQs, short and long. A short IRQ is one which is expected to take
a very short period of time, during which the rest of the machine will be blocked and
</p><!-- l. 1954 --><p class='indent'> Under Linux, hardware interrupts are called IRQs (Interrupt ReQuests). There
are two types of IRQs, short and long. A short IRQ is one which is expected to take a
very short period of time, during which the rest of the machine will be blocked and
no other interrupts will be handled. A long IRQ is one which can take longer, and
during which other interrupts may occur (but not interrupts from the same
device). If at all possible, it is better to declare an interrupt handler to be

View File

@ -5392,9 +5392,9 @@ interrupts, is much harder to implement because it has to be dealt with when
convenient for the hardware, not the CPU. Hardware devices typically have a very
small amount of RAM, and if you do not read their information when available, it is
lost.
</p><!-- l. 1954 --><p class='indent'> Under Linux, hardware interrupts are called IRQs (Interrupt ReQuests). There
are two types of IRQs, short and long. A short IRQ is one which is expected to take
a very short period of time, during which the rest of the machine will be blocked and
</p><!-- l. 1954 --><p class='indent'> Under Linux, hardware interrupts are called IRQs (Interrupt ReQuests). There
are two types of IRQs, short and long. A short IRQ is one which is expected to take a
very short period of time, during which the rest of the machine will be blocked and
no other interrupts will be handled. A long IRQ is one which can take longer, and
during which other interrupts may occur (but not interrupts from the same
device). If at all possible, it is better to declare an interrupt handler to be