home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!horse.ee.lbl.gov!torek
- From: torek@horse.ee.lbl.gov (Chris Torek)
- Newsgroups: comp.unix.wizards
- Subject: Re: a novice unix internals question
- Date: 31 Dec 1992 23:43:43 GMT
- Organization: Lawrence Berkeley Laboratory, Berkeley CA
- Lines: 12
- Message-ID: <28186@dog.ee.lbl.gov>
- References: <1992Dec16.081648.22123@sbcs.sunysb.edu> <1992Dec20.225210.9418@thunder.mcrcim.mcgill.edu> <1992Dec21.171809.11037@fokus.gmd.de>
- NNTP-Posting-Host: 128.3.112.15
-
- In article <1992Dec21.171809.11037@fokus.gmd.de> jbm@fokus.gmd.de
- (Joerg Micheel) writes:
- >It's true that the interrupt thread is completely unrelated to the process
- >running, but the process gets charged for the time of interrupt processing
- >(see the statement in kern_clock.c to hardclock()).
-
- Fixed in 4.4BSD, at least on machines that have a separate hardware timer
- (e.g., hp300, sparc, but not i386). Come to USENIX to hear my talk about
- this. :-)
- --
- In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
- Berkeley, CA Domain: torek@ee.lbl.gov
-