Podcast
Questions and Answers
What does the thread library do when a system call is made to change the signal mask for a particular signal?
What does the thread library do when a system call is made to change the signal mask for a particular signal?
- Instructs the user level threads to update their signal mask
- Enables the signal for all kernel level threads simultaneously
- Disables the signal for all kernel level threads simultaneously
- Changes the signal mask for each kernel level thread one by one (correct)
In the context of signal handling, why are updates of the signal mask considered cheap?
In the context of signal handling, why are updates of the signal mask considered cheap?
- They do not affect the performance of the thread library (correct)
- Signals themselves occur more frequently
- They occur at the kernel level
- They require frequent system calls
When a user level thread decides to re-enable a particular signal, what action does the user level library take?
When a user level thread decides to re-enable a particular signal, what action does the user level library take?
- Instructs kernel level threads to avoid updating their signal masks
- Notifies the kernel level thread to update its signal mask for that specific signal (correct)
- Halts all system calls temporarily
- Instructs kernel level threads to disable all signals
Why does updating the signal mask for each kernel level thread one by one optimize performance?
Why does updating the signal mask for each kernel level thread one by one optimize performance?
What is the reason behind the need to update signal masks for kernel level threads one by one?
What is the reason behind the need to update signal masks for kernel level threads one by one?
How does the user level library optimize for the common case in managing signals?
How does the user level library optimize for the common case in managing signals?
What distinguishes updates of the signal mask from handling signals directly?
What distinguishes updates of the signal mask from handling signals directly?
In managing signals, why are updates of the signal mask made at the user level?
In managing signals, why are updates of the signal mask made at the user level?
Why does each kernel level thread have its signal mask updated individually?
Why does each kernel level thread have its signal mask updated individually?
What is the primary reason for running through the process of updating signal masks for each kernel level thread one by one as signals come in?
What is the primary reason for running through the process of updating signal masks for each kernel level thread one by one as signals come in?
