List reasons why a Mode switch between threads may be
cheaper than a Mode switch between processes.
- 1 Answers
- 4203 Views
- I also Faced
- E-Mail Answers
Answer Posted / kumar
1. reason - the control blocks for processes are larger
than for threads (hold more
state information), so the amount of information to
move during the thread
switching is less than for process context
switching
2. reason - the major reason is that the memory management
is much simpler for
threads than for processes. Threads share their memory so
during mode switching, memory information does not have to
be exchanged/changed, pages and page tables do not have to
be switched, etc. This makes the thread context switch much
cheaper than for processes. In case of processes the memory
pieces (pages) need to be exchanged, etc. (Will talk about
the details in few weeks).
3. reason - threads do not have to worry about accounting,
etc, so do not have to fill
out all the information about accounting and other
process specific information in
their thread control block, so keeping the thread
control block consistent is much
faster
4. reason - threads share files, so when mode switch
happens in threads, these
information stay the same and threads do not have to worry
about it (similar to accounting information) and that
makes the mode switch much faster.
But the most expensive operation is truly the memory
aspect.
| Is This Answer Correct ? | 3 Yes | 0 No |
Post New Answer View All Answers
How will you check if your R3 system is 32bit or 64bit?
Explain page fault interrupt?
Is 100 cpu usage bad?
What is waiting time?
Differentiate between the user mode and monitor mode.
Explain Page Segmentation.
What is external fragmentation?
What are the four common types of files?
Are 64bit applications faster?
What is git bash?
What's the difference between x86 and x64?
What is Direct Access Method?
Does a clean install erase everything?
What is the most used operating system?
Describe horizontal scalability and vertical scalability.
