The Nevercrash Operating System Company has been receiving complaints from some of its customers about its latest release, which includes semaphore operations. They feel it is immoral for processes to block (they call it "sleeping on the job"). Since it is company policy to give the customers what they want, it has been proposed to add a third operation, peek, to supplement up and down. peek simply examines the semaphore without changing it or blocking the process. In this way, programs that feel it is immoral to block can first inspect the semaphore to see if it is safe to do a down. Will this idea work if three or more processes use the semaphore? If two processes use the semaphore?

The Nevercrash Operating System Company has been receiving complaints from some of its customers about its latest release, which includes semaphore operations. They feel it is immoral for processes to block (they call it "sleeping on the job"). Since it is company policy to give the customers what they want, it has been proposed to add a third operation, peek, to supplement up and down. peek simply examines the semaphore without changing it or blocking the process. In this way, programs that feel it is immoral to block can first inspect the semaphore to see if it is safe to do a down. Will this idea work if three or more processes use the semaphore? If two processes use the semaphore?

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

You must determine the location of a procedure whose name you only partially recall.The issue: Do you "sort of" know what process you're looking for's name? Because the procedures in the Windows API have incredibly inconsistent names, this is a common issue for coders who work with Microsoft Windows. Not much better are UNIX coders. The only issue is that UNIX prefers to omit letters from system call names, so only the inconsistent naming conversions are constant. (for example, creat).
How does "many threads" differ from "many processes"? If it is not too much bother, it would be much appreciated if you could expound on this point in a phrase or two.
You must locate a procedure for which you only know a portion of the name.The Issue: You "sort of" know the name of the process you're looking for. Because of the highly inconsistent naming convention of the procedures in the Windows API, this is a frequent problem for Microsoft Windows programmers. No superior are UNIX programmers. Only the inconsistency in naming conversions is constant; the only issue is that UNIX enjoys leaving letters out of system call names. (for example, creat).
Is it possible for a single process to get stuck in the middle of its execution? Please provide justifications for your responses.
Give a programmer's perspective on why deep access is preferable to shallow access; don't focus just on performance.
A comparison is made between two different processes and two separate threads in the same process. When you know what to do and when to do it, it's always simpler.
It's possible that there are scenarios where threads run at the user level are preferred to those run by the kernel. How can threads at the user level and the kernel level diverge? Is there a case in which one kind performs better than the others?
What system resources are used when a new thread is started? That they are not involved in the process of creating a method is what sets them apart. ..
For a number of reasons, threads are viewed as "lightweight" processes. What are the prerequisites for starting a new thread? They're employed in a different way from the ones used to build a process.
The Nevercrash Operating System Company has been receiving complaints from some of its customers about its latest release, which includes semaphore operations. They feel it is immoral for processes to block (they call it "sleeping on the job"). Since it is company policy to give the customers what they want, it has been proposed to add a third operation, peek, to supplement up and down. peek simply examines the semaphore without changing it or blocking the process. In this way, programs that feel it is immoral to block can first inspect the semaphore to see if it is safe to do a down. Will this idea work if three or more processes use the semaphore? If two processes use the semaphore?
What is the difference between loading a driver as a module and directly integrating it into the kernel? Contrast the advantages and disadvantages of different techniques for adding a driver.
Is it possible to terminate one process while it is still executing a different process? Explain your responses if you can.