MESSAGE
| DATE | 2015-02-04 |
| FROM | Ruben Safir
|
| SUBJECT | Subject: [LIU Comp Sci] (fwd) Operating System Design
|
From owner-learn-outgoing-at-mrbrklyn.com Wed Feb 4 13:19:43 2015
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix)
id 9CA4616116B; Wed, 4 Feb 2015 13:19:43 -0500 (EST)
Delivered-To: learn-outgoing-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 28)
id 7660316115D; Wed, 4 Feb 2015 13:19:43 -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 6BB8616115D
for ; Wed, 4 Feb 2015 13:19:42 -0500 (EST)
Received: from panix2.panix.com (panix2.panix.com [166.84.1.2])
by mailbackend.panix.com (Postfix) with ESMTP id 72FB6137C6
for ; Wed, 4 Feb 2015 13:19:41 -0500 (EST)
Received: by panix2.panix.com (Postfix, from userid 20529)
id 6291833CC5; Wed, 4 Feb 2015 13:19:41 -0500 (EST)
From: Ruben Safir
To: learn-at-nylxs.com
Subject: [LIU Comp Sci] (fwd) Operating System Design
User-Agent: tin/2.0.0-20110823 ("Ardenistiel") (UNIX) (NetBSD/6.1.5 (i386))
Message-Id: <20150204181941.6291833CC5-at-panix2.panix.com>
Date: Wed, 4 Feb 2015 13:19:41 -0500 (EST)
Sender: owner-learn-at-mrbrklyn.com
Precedence: bulk
Reply-To: learn-at-mrbrklyn.com
-- forwarded message --
Path: reader1.panix.com!panix!not-for-mail
From: ruben safir
Newsgroups: comp.os.linux.hardware
Subject: Operating System Design
Date: Thu, 29 Jan 2015 17:11:59 -0500
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 38
Message-ID:
NNTP-Posting-Host: 96.57.23.82
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: reader1.panix.com 1422569519 29417 96.57.23.82 (29 Jan 2015 22:11:59 GMT)
X-Complaints-To: abuse-at-panix.com
NNTP-Posting-Date: Thu, 29 Jan 2015 22:11:59 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
Xref: panix comp.os.linux.hardware:364723
I'm wondering if anyone has a background in operating system design.
I'm taking a class is OS's and the text is
OPERATING
SYSTEM
CONCEPTS
ABRAHAM SILBERSCHATZ
9th edition, and it says something that is puzzling me
"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
-- end of forwarded message --
|
|
