In §2.2, in the paragraph that begins “In a tradition system, when there are…”, the authors describe an issue that can arise when user-level threads are implemented atop regular kernel-level threads. In particular, they describe a scenario where time could be wasted because a user-level thread is needlessly spin-waiting for a lock.
With scheduler activations, a user-level threading library can prevent this issue from occuring. How? Describe the events that occur in the kernel and the actions that must be taken by the library in user-space.
Local Stanford students should write up their response on a sheet of paper that includes their name. The sheet of paper with the response should be submitted immediately before lecture.
SCPD students should write up their response in a text file named
response.sched-activations.txt and upload it via the submission and grades
page. You’ll need to sign in with your SUNetID to access the page. Ensure that
the file is named exactly response.sched-activations.txt; other filenames will
not be accepted. Responses will be accepted until one week after the
corresponding paper’s lecture.
In either case, the response should be short, likely only a pithy paragraph in length.
Tuesdays and Thursdays
4:30pm - 5:50pm
Gates B1
Dawson
Mondays
3:00pm - 5:00pm
Gates 314
Sergio
Mondays and Wednesdays
6:00pm - 7:30pm
Gates 288
Dawson Engler
Instructor
Gates 314
Sergio Benitez
Instructor
Gates 288
Spring 2015
Spring 2014
Winter 2013
Spring 2013
Spring 2012
Spring 2011
Spring 2010