hello my name is Sean and in this tutorial we shall move on to the process manager and look at how the processor and its manager work to process the jobs being passed through to memory
it is important to understand that process is very in performance speed and bandwidth so results vary from machine to machine
but there are some factors to appreciate the clock speed refers to the speed at which the process of can execute instructions so the quicker the clock speed the more cycles are on and essentially the more instructions are carried out do not always be fooled though the efficiency of the process is architecture determines how much work the processor actually dots
the bandwidths determines how much information can be processed in one instruction the wider the bandwidths the more they can be fitted on and sent think a bit as aid motorway know why do the rogue the more cars or in this case instructions can be run at the same time the processor has its own version of memory also known as cash that exists on the diable processor because it has a less time to travel it is usually checked first before calling in a page from the ram cash can be accessed between 5 to 10 time faster than accessing the ram a process scheduler is in charge of making efficient use of a physical processor there are two parts to this one is the job scheduler and the other is processed scheduler taking notes that a job can consist the many processes it can juggle many jobs a process can be in 5 different states hold ready run wait and finish Hold is controlled by the job scheduler and as the name suggest it is holding the job until it has permission to run think of a car race you cannot start the engine until the starting signal has been cold now when your engine is on you are in a ready state
the Ready state is a signal to continue with the process when the car is ready to proceed it is enough running state in our case it is currently processing the job
for all this time of running there may be a concern of performance so a check with the team is made to ensure it is OK to start running again returning to a Ready state if it is okay to run again it goes back into a running state but what if there is an engine failure It not case an i/o request page fault is presented and the car is pause in a waiting state until it has found the correctly source or part so that it can continue to run This will loop constantly until the process has either completed or fail where it is then put into a finishing state each process has a life cycle the process control block is used as an identifiers and contains basic information about the job what is it doing where is it going how much processing has a correctly done and most importantly how much it has spent in using resources With the use of a process control block we can place those in the correct cues sync up the cues as a linked list of pcb