Although a working implementation is provided, it “busy waits,” that is, it spins in a loop checking the current time and calling thread_yield() until enough time has gone by. Reimplement it to avoid busy waiting.
If your delays seem too short or too long, reread the explanation of the ‘-r’ option to pintos (see Section 1.1.4 [Debugging versus Testing], page 4).
Although a working implementation is provided, it “busy waits,” that is, it spins in a loop checking the current time and calling thread_yield() until enough time has gone by. Reimplement it to avoid busy waiting.
If your delays seem too short or too long, reread the explanation of the ‘-r’ option to pintos (see Section 1.1.4 [Debugging versus Testing], page 4).