MESSAGE
| DATE | 2015-01-29 |
| FROM | Ruben Safir
|
| SUBJECT | Subject: [LIU Comp Sci] Operating System Interupts
|
From owner-learn-outgoing-at-mrbrklyn.com Thu Jan 29 17:04:08 2015
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix)
id BFD9F16116D; Thu, 29 Jan 2015 17:04:08 -0500 (EST)
Delivered-To: learn-outgoing-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 28)
id B0600161174; Thu, 29 Jan 2015 17:04:08 -0500 (EST)
Delivered-To: learn-at-nylxs.com
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
by mrbrklyn.com (Postfix) with ESMTP id 449B016116D
for ; Thu, 29 Jan 2015 17:04:08 -0500 (EST)
Received: from [10.0.0.19] (unknown [96.57.23.82])
by mailbackend.panix.com (Postfix) with ESMTPSA id B531D133E4;
Thu, 29 Jan 2015 17:04:07 -0500 (EST)
Message-ID: <54CAAE57.1030900-at-panix.com>
Date: Thu, 29 Jan 2015 17:04:07 -0500
From: Ruben Safir
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: learn-at-nylxs.com, Samir Iabbassen
Subject: [LIU Comp Sci] Operating System Interupts
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: owner-learn-at-mrbrklyn.com
Precedence: bulk
Reply-To: learn-at-mrbrklyn.com
I just can figure out what this guy is say here. It doesn't make sense.
"Interrupts are an important part of a computer architecture. Each computer
design has its own interrupt mechanism, but several functions are common.
The interrupt must transfer control to the appropriate interrupt service
routine.
The straightforward method for handling this transfer would be to invoke
a generic routine to examine the interrupt information. The routine, in
turn,
would call the interrupt-specific handler. However, interrupts must be
handled
quickly
" Since only a predefined number of interrupts is possible, a table of
pointers to interrupt routines can be used instead*** to provide the
necessary
speed. The interrupt routine is called indirectly through the table, with no
intermediate routine needed. Generally, the table of pointers is stored
in low
memory (the first hundred or so locations). These locations hold the
addresses
of the interrupt service routines for the various devices. This array,
or interrupt
vector, of addresses is then indexed by a unique device number, given with
the interrupt request, to provide the address of the interrupt service
routine for
the interrupting device. Operating systems as different as Windows and UNIX
dispatch interrupts in this manner."
*** Instead of what? Just because you have a table of pointers to
routines doesn't change the need for a routine, a generic routine
perhaps, from accessing that table.
Ruben
|
|
