Skip to main content

Threads vs Processes: Shared vs Isolated State

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface​

  • Open learner-facing unit
  • Curriculum path: content/curriculum/systems/semester-05-os-networking/module-01-processes-scheduling/concepts/cluster-04-context-switching-and-overhead/12-threads-vs-processes-shared-vs-isolated-state-primary.md
  • App: systems
  • Semester: semester-05-os-networking
  • Module: module-01-processes-scheduling
  • Unit kind: concept
  • Curation level: module_curated

Learning objectives​

  • Trace Threads vs Processes: Shared vs Isolated State using the language of processes, scheduling policy, and kernel-visible state.
  • Compare the abstraction in the learner page against concrete scheduler behavior you can observe or reason about on a real system.
  • Use operating-system-concepts, ostep to connect the learner explanation to metrics, tradeoffs, and debugging evidence.

Prerequisites​

  • Comfort reasoning about CPU, memory, and the kernel/user boundary from earlier systems work.

Source books​

  • operating-system-concepts
  • ostep

Source routes​

Operating System Concepts​

Ostep​

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

  • man 7 sched (official_docs_companion) - Anchors scheduler concepts in the actual Linux process scheduling interface and policy vocabulary.
  • Linux Kernel Documentation: Scheduler (optional_deep_dive) - Useful after the learner has the concept page, when they want to see how theory lands in kernel design.

AI companion modes​

  • Explain simply
  • Socratic tutor
  • Quiz me
  • Diagnose my confusion
  • Generate extra practice

Source-of-truth note​

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Threads vs Processes: Shared vs Isolated State, and treat outside material as supporting enrichment only.