Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #13590
| From | Rich <rich@example.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: operating systems design |
| Date | 2015-02-03 21:19 +0000 |
| Organization | My Linux Box |
| Message-ID | <mare1u$c02$1@dont-email.me> (permalink) |
| References | <maeb6o$sn9$1@reader1.panix.com> <map3hb$dcc$3@news.albasani.net> <marcdt122sh@news6.newsguy.com> |
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote: > On 2015-02-03, The Natural Philosopher <tnp@invalid.invalid> wrote: > > I think what he means is that having a set of specific ISRs on a per > > hardware basis is preferable to having one ISR and polling all the > > hardware to find out which one did it, and then vectoring to ITS ISR > On the other hand, you could have a master ISR to which the hardware > presents the address of the interrupting device, and this could be > used to index into a table of vectors to subsidiary ISRs appropriate > to each device. (This table could be built at boot time by scanning > for and identifying attached devices - or, as in the bad old days, > the table could be hard-coded as a result of the sysgen process.) Which is exactly what the second paragraph quoted from the textbook by the OP described. That portion is just implimented in hardware rather than by running software (I'm ignoring microcode to perform the above function right now, which would blur the distinction).
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Find similar | Unroll thread
operating systems design ruben safir <ruben@mrbrklyn.com> - 2015-01-29 17:11 -0500
Re: operating systems design Rich <rich@example.invalid> - 2015-01-29 22:29 +0000
Re: operating systems design ruben safir <ruben@mrbrklyn.com> - 2015-01-30 08:19 -0500
Re: operating systems design "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-01-30 09:01 -0500
Re: operating systems design Robert Heller <heller@deepsoft.com> - 2015-01-30 08:07 -0600
Re: operating systems design Jeroen Belleman <jeroen@nospam.please> - 2015-01-30 15:43 +0100
Re: operating systems design Robert Heller <heller@deepsoft.com> - 2015-01-30 09:09 -0600
Re: operating systems design Rich <rich@example.invalid> - 2015-01-30 15:21 +0000
Re: operating systems design Robert Heller <heller@deepsoft.com> - 2015-01-30 11:27 -0600
Re: operating systems design Rich <rich@example.invalid> - 2015-01-30 19:10 +0000
Re: operating systems design Jean-David Beyer <jeandavid8@verizon.net> - 2015-02-02 08:29 -0500
Re: operating systems design Rich <rich@example.invalid> - 2015-02-02 15:09 +0000
Re: operating systems design The Natural Philosopher <tnp@invalid.invalid> - 2015-02-03 00:11 +0000
Re: operating systems design Jeroen Belleman <jeroen@nospam.please> - 2015-01-30 09:28 +0100
Re: operating systems design The Natural Philosopher <tnp@invalid.invalid> - 2015-02-03 00:08 +0000
Re: operating systems design Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-02-03 20:52 +0000
Re: operating systems design The Natural Philosopher <tnp@invalid.invalid> - 2015-02-03 21:06 +0000
Re: operating systems design Rich <rich@example.invalid> - 2015-02-03 21:19 +0000
csiph-web