Difference between revisions of "Multi-tasking"

From Computer History Wiki
Jump to: navigation, search
m (fix emp)
m (Add links)
Line 1: Line 1:
'''Multitasking''' [[operating system]]s are a subset of operating systems - now, by far the predominant form - which allow multiple programs to run at the same time.
+
'''Multitasking''' [[operating system]]s are a subset of operating systems - now, by far the predominant form - which allow multiple [[program]]s to run at the same time.
  
There are two principal types: '''preemptive multitasking''', in which computations can be (unkownst to them) interrupted in the middle of their work to allow other computations to run, and '''cooperative multitasking''', in which a running computation has to explicitly 'give up' the machine, in order for another computation to run.
+
There are two principal types: '''preemptive multitasking''', in which computations can be (unkownst to them) [[interrupt]]ed in the middle of their work to allow other computations to run, and '''cooperative multitasking''', in which a running computation has to explicitly 'give up' the machine, in order for another computation to run.
  
Note that this relinquishment may be a side effect of something the computation does; e.g. it may call for some input or output, and while waiting for that to happen, some other computation may be run.
+
Note that this relinquishment may be a side effect of something the computation does, not an explicit giveaway; e.g. it may call for some [[input/output]], and while waiting for that to happen, some other computation may be run.
  
 
{{stub}}
 
{{stub}}

Revision as of 15:59, 27 April 2018

Multitasking operating systems are a subset of operating systems - now, by far the predominant form - which allow multiple programs to run at the same time.

There are two principal types: preemptive multitasking, in which computations can be (unkownst to them) interrupted in the middle of their work to allow other computations to run, and cooperative multitasking, in which a running computation has to explicitly 'give up' the machine, in order for another computation to run.

Note that this relinquishment may be a side effect of something the computation does, not an explicit giveaway; e.g. it may call for some input/output, and while waiting for that to happen, some other computation may be run.