Register

Andrew S. Tanenbaum (OS) Edition 4 Exercise 2 Question 16 (Page No. 175)

1,733 views

1 Answer

0 votes
0 votes

Answer:

It is not possible to preempt the User-level threads by the clock until the entire process' quantum is used. But it is possible to preempt the Kernel-level threads individually. In this case, the clock will interrupt the current thread if a thread is running for too long.

After this, the Kernel can pick any other thread from the same process for running, if it wants to run.

User Avatar
Voting & Accepting an answer helps improve the community
← PreviousNext →
← Previous in categoryNext in category →

Related questions

446
views
0 answers
0 votes
admin asked Oct 24, 2019
446 views
Andrew S. Tanenbaum (OS) Edition 4 Exercise 2 Question 22 (Page No. 175)
Suppose that an operating system does not have anything like the select system call to see in advance if it is safe to read from a file, pipe, or ... it possible to implement a threads package in user space under these conditions? Discuss.
User Avatar
1.4k
views
1 answers
0 votes
admin asked Oct 24, 2019
1,367 views
Andrew S. Tanenbaum (OS) Edition 4 Exercise 2 Question 21 (Page No. 175)
Consider a system in which threads are implemented entirely in user space, with the run-time system getting a clock interrupt once a second. Suppose that a clock ... system. What problem might occur? Can you suggest a way to solve it?
User Avatar
1.8k
views
1 answers
0 votes
admin asked Oct 24, 2019
1,801 views
Andrew S. Tanenbaum (OS) Edition 4 Exercise 2 Question 15 (Page No. 175)
Why would a thread ever voluntarily give up the CPU by calling thread yield? After all, since there is no periodic clock interrupt, it may never get the CPU back.
User Avatar
1.1k
views
1 answers
0 votes
admin asked Oct 25, 2019
1,131 views
Andrew S. Tanenbaum (OS) Edition 4 Exercise 2 Question 31 (Page No. 176)
How could an operating system that can disable interrupts implement semaphores?
User Avatar
Link Copied!