Operating System Design

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!ra.nrl.navy.mil!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail
From	ruben safir <ruben@mrbrklyn.com>
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	<maeb7f$sn9$2@reader1.panix.com> (permalink)
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@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	csiph.com comp.os.linux.hardware:2713

Show key headers only | View raw

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

Back to comp.os.linux.hardware | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Operating System Design ruben safir <ruben@mrbrklyn.com> - 2015-01-29 17:11 -0500
  Re: Operating System Design "Vince Coen" <VBCoen@gmail.com> - 2015-01-29 22:29 +0000
  Re: Operating System Design Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-01-29 17:38 -0500
  Re: Operating System Design Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2015-01-29 16:07 -0700
    Re: Operating System Design Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2015-01-29 16:16 -0700
  Re: Operating System Design David Brown <david.brown@hesbynett.no> - 2015-01-30 09:00 +0100
    Re: Operating System Design ruben safir <ruben@mrbrklyn.com> - 2015-02-01 19:34 -0500

csiph-web