Skip to main content

Story of a Program

Image result for process state transition diagram

Hi, I'm a program. I have seen two worlds. People call then "Main Memory" and "Secondary Memory". Secondary Memory is my home, this is where I spend most of the time. It is my Home. Main memory(aka Primary Memory) is my work place, this is the place from where I turn into Action using processor.

I enter the Primary Memory aka Main memory. I have to take a toke and wait in the lounge. This is called as ready state. Some times the lounge gets crowded and few programs from here will be sent to another big lounge, it is called "Ready Suspended". So once we get the chance to enter the processor we move from ready state to "Running" state. While we are running inside processor we may need some resources and we get have to wait for those resources to be available. Then we are sent to another state from the "Running" state. This state is similar to "Ready Suspended ", which we went when we were waiting in the lounge, but this buffer state is within the main memory.This is pretty small place. Sometimes when this gets crowded, we enter the "Blocked Suspended" state which is a bigger place in the secondary memory.

Once the resource get available we are back to "Running", to get up and running. Once the running actions defined in the program are completed we end at a state called "Terminated".



Comments

Popular posts from this blog

ASCII to Decimal conversion

#include "msp430.h"                     ; #define controlled include file         NAME    main                    ; module name         PUBLIC  main                    ; make the main label vissible                                         ; outside this module         ORG     0FFFEh         DC16    init                    ; set reset vector to 'init' label         RSEG    CSTACK                  ; pre-declaration of segment         RSEG    CODE      ...

Event Sourcing with CQRS.

  The way event sourcing works with CQRS is to have  part of the application that models updates as writes to an event log or Kafka topic . This is paired with an event handler that subscribes to the Kafka topic, transforms the event (as required) and writes the materialized view to a read store.

Create One-Click Shutdown and Reboot Shortcuts

First, create a shortcut on your desktop by right-clicking on the desktop, choosing New, and then choosing Shortcut. The Create Shortcut Wizard appears. In the box asking for the location of the shortcut, type shutdown. After you create the shortcut, double-clicking on it will shut down your PC. But you can do much more with a shutdown shortcut than merely shut down your PC. You can add any combination of several switches to do extra duty, like this: shutdown -r -t 01 -c "Rebooting your PC" Double-clicking on that shortcut will reboot your PC after a one-second delay and display the message "Rebooting your PC." The shutdown command includes a variety of switches you can use to customize it. Table 1-3 lists all of them and describes their use. I use this technique to create two shutdown shortcuts on my desktop—one for turning off my PC, and one for rebooting. Here are the ones I use: shutdown -s -t 03 -c "Bye Bye m8!" shutdown -r -t 03 -c ...