-

 

Week 2 – CST– 334 Operating Systems

Module 2 – Process Management

This week’s subject was Processes Manage. A process is a running program.

In chapter 4 of OSTEP, we learned how the operating system creates the illusion of multiple processes running at the same time by virtualizing the CPU using a technique called time-sharing. We also learned about the APIs available in modern systems such as Create, Destroy, wait, miscellaneous controls, and status. This chapter also taught us about the different process states. A process can be in one of three states: running, ready, or blocked. A process that has control of the CPU is considered to be running. A process that is ready, is standing by ready to run but has not been chosen by the OS to run yet. Lastly, a process is blocked when it has performed a procedure that does not make it ready to run such as initiating an I/O request to a disk.

Chapter 5 introduced us to the fork(), exec(), and wait() system calls which deal with UNIX process creation. Fork() is used to create a new process, the creator process is called the parent, and the new process is called the child. Wait() allows the parent to wait for the child to complete execution. The exec() system call allows the child to break away from the parent and create a new program.

Chapter 6 is about limited direct execution. It is a technique used to make programs run fast by making sure to set up the hardware in a way which limits what a process can do without OS assistance. During boot time, the OS sets up trap handlers and starts an interrupt timer. This allows processes to run in restricted mode and require the OS only to perform privileged operations.

Chapter 7 was an introduction to scheduling. We learned about scheduling metrics such as turnaround time and response time. Turnaround time is the time it takes a process to complete. We calculate this by taking the time at which the process is completed and subtracting the time at which it arrived. Response time is the time it takes a process to start. We calculate this metric by taking the time the process starts and subtracting the time at which it arrived. We also learned about the different scheduling algorithms like First In First Out (FIFO), Shortest Job First (SJF), Shortest Time-to-Completion Firsts (STCF), and Round Robin.

Chapter 8 is all about the Multi-Level Feedback Queue. This is a scheduling approach that uses different levels of queues and uses feedback to determine the priority of a process. This process uses 5 rules to manage processes.

Rule 1: If priority (A) > Priority (B), A runs (B doesn’t).

Rule 2: If priority(A) = Priority (B), A&B run in round-robin fashion.

Rule 3: When a job enters the system, it is placed at the highest priority.

Rule 4: Once a job uses up its time allotment at a given level (regardless of how many times it has given up the CPU), its priority is reduced (i.e., it moves down one queue).

Rule 5: After some time period S, move all the jobs in the system to the topmost queue.

 

Comments

Post a Comment

Popular posts from this blog

-
Image
  Week 2- CST-300 Module 2 OLI – Module 2 This week’s module focused on collective intelligence, reading the mind in the eyes, behavior of good teams, and why team skills will help after graduation. Collective intelligence illustrated how teams that have better collaboration skills were more successful. Meaning that everyone participated and contributed to complete the task or project. Some key features of successful teams were equal participation, higher number of women, and social sensitivity. I enjoyed the reading the mind in the eyes activity. It is difficult to tell a person’s emotions by examining just their eyes and not the entire face or body language. I scored about average. I will continue to participate and share my thoughts and ideas on topics being discussed in my team. Behaviors of good teams was a research article done at google looking for the perfect team. They found that teams promote better job satisfaction, better problem solutions and faster innovation.
Read more
-
Image
  Week 1- CST-300 Module 0 & 1 Team Resume Hello and welcome to my first post. This is a screen shot of our team resume. Although we ran into issues with some members missing, we eventually joined with another group and managed to collaborate on this assignment. Our team did an excellent job with their bios and completed the assignment on time. Module 1 Lecture   The readings from module 1 taught me about CSUMB's history and vision statement. It also covered the Degree programs from the School of Computing and Design and its faculty. The lecture also included a video titled "Study Tips to Succeed as an Online Student." The video taught me that I will need to read the syllabus, plan weekly study times, connect with classmates, check canvas frequently, and ask questions to be successful in this class.   Module 1 Lab   The lab for this week explains the American Psychological Association (APA) writing style. APA is the style used by the Computer Science departmen
Read more
-
  Week 3- CST-300 Module 3   OLI – Module 3 This week’s module is titled “What do You Bring to the Team?” and it is made up of six sections. The first section was Processing Styles and Diversity Communication. It explains approaches that would help an internal processor in your team. Some examples were to think silently for a minutes before discussing for answers, ask if members need more time before responding, and use email to communicate. The second section was Work Styles. Here we learned about work styles Get it Right – Task oriented, Get it Done – Task oriented, Get Along – people oriented, and Get Appreciation – People oriented. Each style had its strengths and weaknesses and we had to figure out how to balance them or how to help others with a different style. The third section was Your Booth Team Members. Here we watched a video of each booth member. We were then tasked with ways to support each member’s work style. The fourth section was Conflict Styles. It focuse
Read more