Typically, at the completion of a device I/O, a single interrupt is raised and appropriately handled by the host processor. In certain settings, however, the code that is to be executed at the completion of the I/O can be broken into two separate pieces, one of which executes immediately after the I/O completes and schedules a second interrupt for the remaining piece of code to be executed at a later time. What is the purpose of using this strategy in the design of interrupt handlers?
Typically, at the completion of a device I/O, a single interrupt is raised and appropriately handled by the host processor. In certain settings, however, the code that is to be executed at the completion of the I/O can be broken into two separate pieces, one of which executes immediately after the I/O completes and schedules a second interrupt for the remaining piece of code to be executed at a later time. What is the purpose of using this strategy in the design of interrupt handlers?
Chapter6: System Integration And Performance
Section: Chapter Questions
Problem 28VE
Related questions
Question
![Typically, at the completion of a device I/O, a single interrupt is raised and
appropriately handled by the host processor. In certain settings, however, the
code that is to be executed at the completion of the I/O can be broken into two
separate pieces, one of which executes immediately after the I/O completes and
schedules a second interrupt for the remaining piece of code to be executed at a
later time. What is the purpose of using this strategy in the design of interrupt
handlers?](/v2/_next/image?url=https%3A%2F%2Fcontent.bartleby.com%2Fqna-images%2Fquestion%2Fee6fb2ef-61e1-41e1-8428-575b8fc47c90%2F8760fd88-c2bf-4b34-ac1e-a600f87d8af9%2Fy5kfq9d_processed.jpeg&w=3840&q=75)
Transcribed Image Text:Typically, at the completion of a device I/O, a single interrupt is raised and
appropriately handled by the host processor. In certain settings, however, the
code that is to be executed at the completion of the I/O can be broken into two
separate pieces, one of which executes immediately after the I/O completes and
schedules a second interrupt for the remaining piece of code to be executed at a
later time. What is the purpose of using this strategy in the design of interrupt
handlers?
Expert Solution
![](/static/compass_v2/shared-icons/check-mark.png)
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 2 steps
![Blurred answer](/static/compass_v2/solution-images/blurred-answer.jpg)
Knowledge Booster
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.Recommended textbooks for you
![Systems Architecture](https://www.bartleby.com/isbn_cover_images/9781305080195/9781305080195_smallCoverImage.gif)
Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning
![Systems Architecture](https://www.bartleby.com/isbn_cover_images/9781305080195/9781305080195_smallCoverImage.gif)
Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning