Interrupts

5 pts.
Tags:
I/O
Interrupts
What is a difference between short I/O interrupt and long I/O interrupt?

Software/Hardware used:
Software

Answer Wiki

Thanks. We'll let you know when a new response is added.

How about the length of time of the interrupt.  ;-)

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Michael Tidmarsh
    Welcome to ITKE, AdilMujeeb! Here's a definition from Whatis.com that should point you in the right direction.

    For more information on our community, check out our FAQ.
    29,480 pointsBadges:
    report
  • TomLiotta
    This is my very basic understanding. (I don't do much work at the low level of I/O interrupts.) The source code lines for a program will all be compiled (or interpreted) into what might be a long series of machine instructions. At some point, a machine instruction will request actual I/O from some device. Later instructions are going to use whatever data will be brought into memory by the I/O.   However, the amount of time it takes for the I/O to finish is much more than the time it takes for machine instructions to run. Many machine instructions can be run before I/O makes data available.   The source line that asks for I/O can have machine instructions after the one that requests the actual machine I/O. Those instructions can usually continue to run while the I/O is happening. It will usually be machine instructions from a later source line that need to wait for the data, and those might be much later in the instruction stream, especially if optimization has been applied.   In addition, there are almost always other programs running in the system. Machine instructions in those programs don't have to wait at all for the first I/O to finish. They are busy doing unrelated work, so the OS can turn control over to those programs for a time.   A short I/O wait is generally one that allows other machine instructions to run. A long I/O wait can happen when a second I/O request is made while an earlier I/O request is still happening. The second one might not be able even to begin until the first is done if they are competing for the same device.   A long I/O wait generally is one that forces a stop in an instruction stream because an earlier I/O has not signalled its completion yet. The second series of machine instructions won't know if they can continue until the second I/O request has a known state. The inability to run additional machine instructions means that a very long relative period of time must pass before useful work can continue.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following