I published a new wiki article exploring what a thread really is from the CPU's perspective.
Instead of treating a thread as just "a lightweight process," I break down the low-level pieces that actually make it work:
• Virtual memory and address spaces
• Memory pages and how they're used
• The instruction pointer (where execution resumes)
• The stack pointer and per-thread stacks
• Why multiple threads share an address space but maintain independent execution state
• How these concepts distinguish threads from processes
If you've ever wondered what the operating system actually switches during a context switch, or how the CPU knows where a thread continues execution, this article connects those pieces together.
Read it here:
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)