what are the Architectural differences between User-space
threads, and Kernel-supported threads.
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 |
What is the working set of a process?
what is Context switch?
Explain similarities between thread and process?
What is protection boundary?
What is Critical section?
When should we use thread-safe "_r" library calls?
How would you kill a process?
Explain what are the main families of threads?
Explain what is scheduling?
tell me similarities between thread and process
explain about the initial process sequence while the system boots up?
If your server is running on Unix and one of the sessions are keep on running without loading any data. how would you kill it?