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.

What are the pros and cons of using circuit switching?

1217

---

How do I run chkdsk?

1066

---

What is a safe state and its’ use in deadlock avoidance?

1115

---

What is drawback of mvt?

1150

---

How do I know if my ram is corrupted?

1062

---

Explain the basic functions of process management.

1190

---

How do you kill pid?

944

---

What is the safest computer operating system?

1141

---

Can I change operating systems on my laptop?

981

---

What's the difference between x86 and x64?

1056

---

What is memory-management unit (mmu)?

1092

---

What is x32 and x64?

931

---

Explain busy waiting in operating system (os)?

1103

---

What resources are used when a thread created?

1020

---

What is the difference between folder and directory?

1009

---