Thus far it is possible that we’ve made the assumption that a process usually runs to completion and then the OS runs other processes. As indicated in our process management note/discussion we now know this to be false.

It is possible for an OS to be implemented as a timing mechanism, switching between each process after say 100 instructions being executed. In theory, this is a good first approach if all instructions are executed in  a very short and equal timeframe.

Below, we  represent how this can be accomplished by observing what the cpu processes assuming each instruction takes about 1 second for 2 processes, P1 and P2:

Order of execution	Process/operation category	Instructions executed	Time taken (s)
1	I/O	I/O for OS and P1	2
2	P1	100 lines from P1	100
3	I/O	I/O for OS and P2	2
4	P2	100 lines from P2	100
. . . . .	. . . . .	. . . . .	. . . . .
501	I/O	I/O for OS and P1	2
502	P1	100 lines from P1	100
503	I/O	I/O for OS and P2	2
504	P2	100 lines from P2	100
. . . . .	. . . . .	. . . . .	. . . . .

In practice though, a single instruction from a running process can  be waiting or very long, such as when the instruction requires data be read from a secondary storage medium.  Data access on secondary storage is very slow.  Let us assume that P1 has  a few instructions that require some data access. Our table now becomes:

Order of execution	Process/operation category	Instructions executed	Time taken (s)
1	I/O	I/O for OS and P1	2
2	P1	100 lines from P1	1500
3	I/O	I/O for OS and P2	2
4	P2	100 lines from P2	100
. . . . .	. . . . .	. . . . .	. . . . .
501	I/O	I/O for OS and P1	2
502	P1	100 lines from P1	1200
503	I/O	I/O for OS and P2	2
504	P2	100 lines from P2	100
. . . . .	. . . . .	. . . . .	. . . . .

We observe in this analogy that p1 runs for a total of 1502 seconds P2 for 102, P1 for 1202 seconds, P2 for 102 seconds.

To the end user, It appears as if BOTH processes are running slowly, in the long run, p2 can appear to be running in slow motion!

To solve this problem, we could use a system of interrupts, i.e, interrupt the CPU whenever we anticipate a waiting period (for whatever reason I/O, system errors, device errors etc.)

In our analogy, every time P1 needs to wait on data from secondary access, we could put the rest of P1 in a waiting/blocked state and start processing P2.  When the hardware is finished gathering the data for P1, it could interrupt the execution of P2 and return control to P1.

Omitting IO from the OS, An illustration of this example is shown below:

(Assume that instructions for p1 are executed in 1 second intervals until an instruction needing secondary data access is reached)

P1’s instruction include:

49 short instructions then,

1 long access instruction then,

24 short instructions then,

1 long access instruction, then

25 short instructions

Order of execution	Process/operation category	Instructions executed	Time taken (s)
1	P1	50 lines from P1	50
2	OS	(P1 Blocked),	–
3	P2	100 lines from P2	100
4	P2	100 lines from P2	100
5	P2	100 lines from P2	100
6	P2	50 lines from P2, interruption occurs	50
7	P1	25 lines from P1	25
8	OS	(P1 Blocked),	–
9	P2	50 lines from P2	50
10	P2	100 lines from P2	100
11	P2	100 lines from P2	100
12	OS	Interruption occurs to return accessed data to P1	–
13	P1	25 lines from P1	25
14	P2	100 lines from P2	100
. . . . .	. . . . .	. . . . .	. . . . .

We now observe both processes running efficiently with no excessive wait times.

Exercise

1. What is the total wait time for P1 and P2 Respectively?
2. Which process had the more instructions executed?

© 2022  Vedesh Kungebeharry. All rights reserved. 

•  

Multiple programs are usually executed concurrently  as processes (running programs).  A bit of code from each process is executed at a time  on the processor so that all processes are continually executed until system shutdown or they have completed their task and exit.

The operating system  (OS) is programmed to start the execution of programs and manage their execution by putting them into different states.  Note that the programs can be application programs intended for the end user or system programs used for self management (e.g memory management)

Discussion:

1. Virtual memory / page files used to simulate ram capacities larger than physical ram on the main system. (Falls under memory management).
2. Blackboard  as Ram chiselled tablet as Secondary storage – How processes react when they must wait

Process States.

Running – The process is currently being executed

Ready  – A previously interrupted process that can be expected to resume.

Waiting/blocked  – a process that has been put to wait by the cpu or is waiting on a slower operation (I/O or request for data)

Attributions to media used in post

MrDrBob, CC BY-SA 3.0, via Wikimedia Commons

© 2022  Vedesh Kungebeharry. All rights reserved. 

This is the process of loading and executing the basic instructions to load the operating system to bring the system to a fully functional state  to be used for its intended purpose (initiated either by the user powering on the system or an autonomous system system e.g a network device , typically a router. See wake on lan)  .  For modern day systems, these instructions are usually hardcoded in the EEPROM.

Updates to this post

2023-09-15 – Added wake on LAN, and detailed to the initiation of the device.

© 2022  Vedesh Kungebeharry. All rights reserved.