Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!agate!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.internals
Subject: Re: Scheduling of processes, and timers
Message-ID: <14439@dog.ee.lbl.gov>
Date: 18 Jun 91 20:01:51 GMT
References: <1991Jun13.141021.1@sdl.mdcbbs.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 31
X-Local-Date: Tue, 18 Jun 91 13:01:51 PDT

In article <1991Jun13.141021.1@sdl.mdcbbs.com> daniel@sdl.mdcbbs.com writes:
>... developed on Sparcstations running SunOs4.1, but should work on other
>Unix variants. ... Is scheduling likely to take place at system calls ?

Yes.

>        Is there a way round this if this is so ?

No (at least, not without major kernel changes).

>        Do I just give up and use gprof ?

Probably.  You can implement your own profiler; gprof is simply convenient
(see profil(2)).

> 2) The timer resolution on a Sparc 2 is 100Hz ...

This is purely a software issue on the SparcStations.  The actual timers
count in microseconds.  Of course, the software in question is the kernel;
you need kernel source to change it.

>        Is there any other timer available on Sparcstations ?

SparcStations have two timers, one intended for use as the scheduling
clock (often set to interrupt 100 times a second) and one intended for
use as a profiling clock (it interrupts at a much higher priority, and
can be set differently).  Ideally gprof will use the profiling clock,
running at a higher rate.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov