what are the Architectural differences between User-space
threads, and Kernel-supported threads.
- 1 Answers
- 6551 Views
- I also Faced
- E-Mail Answers
Answer / guest
User-space threads live without any support from the
kernel; they maintain all of their state in user space.
Since the kernel does not know about them, they cannot be
scheduled to run on multiple processors in parallel.
Kernel-supported threads fall into two classes.
In a "pure" kernel-supported system, the kernel is
responsible for scheduling all threads.
Systems in which the kernel cooperates with a user-level
library to do scheduling are known as two-level, or hybrid,
systems. Typically, the kernel schedules LWPs, and the user-
level library schedules threads onto LWPs.
Because of its performance problems (caused by the need to
cross the user/kernel protection boundary twice for every
thread context switch), the former class has fewer members
than does the latter (at least on Unix variants). Both
classes allow threads to be run across multiple processors
in parallel.
| Is This Answer Correct ? | 3 Yes | 0 No |
Explain the architectural differences between user-space threads, and kernel-supported threads?
Explain what is protection boundary?
How to work unix commands on windows xp without installing unix o/s in pc?
Explain how to work unix commands on windows xp without installing unix o/s in pc?
List the system calls used for process management?
What is the window of the working set of a process?
Explain the different kinds of threads?
What is Critical section?
When should we use thread-safe "_r" library calls?
what are the Performance differences between User-space threads and Kernel-supported threads.
Protection boundary??
how to edit the network interface device type in container(zone) in solaris 10?
Unix Commands 
