Do page faults present a problem for user-level threads implementations?
What will be an ideal response?
If a process with a user-level threads implementation takes a page fault, then by default the kernel will
deschedule the entire process. In principle, the kernel could instead generate a software interrupt in the process,
notifying it of the page fault and allowing it to schedule another thread while the page is fetched.
You might also like to view...
What is the purpose of the Secure tab on a switch?
a. The switch port will use port discovery to assign a MAC address to the port. b. The switch port will automatically disable itself if a device with a different MAC address connects to the port. c. The switch port will use a different MAC address than the one connected to the port. d. This enables the switch to select what networking devices have a selectable IP address.
What is a connected graph?
a. An undirected graph is connected when there is a path between every pair of vertices b. An undirected graph is connected when there are not more than 1 unreachable vertex c. It's another name for a directed graph d. It's another name for an undirected graph
__________ refers to when an instruction is fetched from a unit of memory, it is likely that in the near future additional instructions will be fetched from that same memory unit.
A. Data spatial locality B. Instruction spatial locality C. Data temporal locality D. Instruction temporal locality
In the class BinaryNode, which of the following methods are specified as type bool?
a. isLeaf b. setItem c. setLeftChildPtr d. getLeftChildPtr