Path: utzoo!mnetor!uunet!husc6!mailrus!ames!hao!gatech!uflorida!codas!novavax!hcx1!hcx3!gwp
From: gwp@hcx3.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Unix Interrupts
Message-ID: <48200002@hcx3>
Date: 18 Feb 88 16:07:00 GMT
References: <3617@mtgzz.UUCP>
Lines: 27
Nf-ID: #R:mtgzz.UUCP:3617:hcx3:48200002:000:1228
Nf-From: hcx3.UUCP!gwp    Feb 18 11:07:00 1988


} /* Written  2:08 pm  Feb 15, 1988 by avr@mtgzz.UUCP (Adam Reed)

} In article <3102@cup.portal.com>, Chuck_SirVAX_Staatse@cup.portal.com writes:
}> Does anyone know if UNIX supports a "Connect to Interrupt" facillity
}> similar to VMS or RSX. Failing an "Out of the Box" solution, has
}> anyone cobbled something together? Target system is a 68000 VME based
}> system.  Any takers?

} UNIX provides a facility called "signals". [ ..]
} , but it is trivially simple to write a device
} driver which will send the appropriate signal, to processes that have
} opened it, when device receives an interrupt.

This is correct, but may not be what is needed, depending upon the
performance constraints involved.  UNIX signals are notoriously slow,
and if the concerned process needs to run in anything less than 200
microseconds or so (your mileage may vary) after the device triggers
the interrupt, you can forget it.  Of course "Chuck" didn't say
whether there where any time constraints involved.
	 _____________________________ 
	| Gil Pilz                    |
	| Harris Computer Systems Div.|
	| 2101 W. Cypress Creek Rd.   |
	| Ft. Lauderdale, FL  33309   |
	| UUCP:gwp@ssd.harris.com     |
	 -----------------------------