When using a multithreaded operating system, a program (like Google Chrome) is managed by a single process, which is responsible for spawning all of the threads. Explain both the positive and negative effects that adopting this multithreading technology may have on the program if you choose to use it.

When using a multithreaded operating system, a program (like Google Chrome) is managed by a single process, which is responsible for spawning all of the threads. Explain both the positive and negative effects that adopting this multithreading technology may have on the program if you choose to use it.

Systems Architecture

7th Edition

ISBN:9781305080195

Author:Stephen D. Burd

Publisher:Stephen D. Burd

Chapter11: Operating Systems

Section: Chapter Questions

Problem 11VE

See similar textbooks

Similar questions

When using a multithreaded operating system, a programme (like Google Chrome) is managed by a single process, which is responsible for spawning all of the threads. Explain both the positive and negative effects that adopting this multithreading strategy may have on the programme if you choose to do so.
Consider a scenario in which the operating system creates processes and threads in response to user input.
Examine the distinction between threads run by the kernel and those run by the user.
Threads are minute, individual parts of a greater whole. Each thread is a component of the larger process, which is another way of stating that a process may be broken down into several threads. The practice of running many processes simultaneously inside the same program, or "process," at the same time is known as "multithreading" in the computer world. There's an important role for multithreading that has to be clarified.
What's the difference between a thread running in the user's process space and one running in the kernel? Is there a favored species among the alternatives?
This may be accomplished by analyzing the scheduling of processes and threads side by side and comparing and contrasting the two.
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.
This question is from Operating Systems. I just need clarification on a question the book didn't throughouly the concept. I tried reading the book and I can really only find one reason for the ULTs. Questions: 1) If a process exits and there are still of that process running, will they continue to run? 2) When a User-level-thread (ULT) executes a system call, why is that thread blocked, but also all the other threads within the process are blocked?
Is it more efficient to employ threads that operate at the user level as opposed to those that operate at the kernel level? What sets apart threads that run on the user level from those that run on the kernel level? Is there ever a point in time when one kind is more advantageous than another?
Two key characteristics separate user-level threads from those in the kernel. What are the benefits and drawbacks of each kind, specifically?
Threads are regarded as "lightweight" processes for a number of reasons. What are the prerequisites for starting a new thread? They are not the same as the ones needed to build a process.
Is there ever a scenario where threads managed by the user, as opposed to the kernel, would be preferable?