Path: utzoo!mnetor!tmsoft!torsqnt!hybrid!scifi!bywater!uunet!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.programmer Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...) Message-ID: <7624@sugar.hackercorp.com> Date: 27 Jan 91 09:47:39 GMT References: <17210@cbmvax.commodore. <1991Jan17.204425.8037@ncsuvx.ncsu.edu> <7564@sugar.hackercorp.com> <1991Jan23.104720.24057@ncsuvx.ncsu.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 15 In article <1991Jan23.104720.24057@ncsuvx.ncsu.edu> kdarling@hobbes.ncsu.edu (Kevin Darling) writes: > Not enough to worry over. I'd say that process selection and switching > really doesn't happen very often, cpu-timewise. Hit me up with a good case. Real-time in general, but if you want a specific case... hmmm... Multi-task MIDI handling. We've had 1200 MIDI messages a second go through a fairly long chain of handlers, which implies lots of context switches. I didn't actually instrument it to determine if context switch time was significant, but in a real-time environment it's generally accepted that you need to have context switches being on the same order of magnitude as subroutine calls. -- Peter da Silva. `-_-' .