How fork() duplicates a process without copying its memory…
0 reactions
How fork() duplicates a process without copying its memory
A visual explainer on how copy-on-write makes `fork()` cheap.
A 10 GB process can fork almost instantly because Linux copies the page tables, shares the physical pages, marks them read-only, and only copies a page when one of the processes writes to it.
It also covers `fork()` \+ `exec()`, how Redis snapshots work, Android Zygote, lazy zero pages, and some CVEs
#dev #programming #technology
A visual explainer on how copy-on-write makes `fork()` cheap.
A 10 GB process can fork almost instantly because Linux copies the page tables, shares the physical pages, marks them read-only, and only copies a page when one of the processes writes to it.
It also covers `fork()` \+ `exec()`, how Redis snapshots work, Android Zygote, lazy zero pages, and some CVEs
#dev #programming #technology
| 3,000 mlx | |
| 4 | |
| 0 |