Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
1

How and Why fork() Uses Copy-on-Write

from Confessions of a Code Addict [alt+shift+b] in programming

In this video, we look at why fork() needs copy-on-write, how it works inside the kernel, and a memory usage problem that Instagram encountered with Python.
4 hours ago

Stay updated

Get a weekly newsletter with the top 5 articles worth reading every week.

More from Confessions of a Code Addict

How Copy-on-Write Works with Memory-Mapped Files

Let’s step inside the kernel and understand how it implements copy-on-write and what are its implications for the performance of user-space systems

5 days ago • 1 votes
x86 Addressing Modes, Part 2: Indirect, Indexed, and Offset-based Modes

In this final part on addressing modes, we learn about indirect, indexed and offset-based addressing modes along with some interesting examples and exercises.

9th Aug 2026 • 1 votes
Why Git Has a Variable Named false_but_the_compiler_does_not_know_it

A small C trick that keeps Clang from flagging valid code as unreachable

3rd Jun 2026 • 1 votes
Virtual Memory: A Deep Dive into Page Tables, TLBs, and Linux Internals

From page faults to NUMA topology: how the Linux kernel manages memory, and what that means for the performance of data-intensive systems.

10th May 2026 • 1 votes

More in programming

What we lost when we lost comments

Comments require commitment, but they’re worth it.

10 hours ago • 1 votes
Lighthouse map

Lovely global map with animated lights sweeping the waters

12 hours ago • 1 votes
GitHub repository landing pages now show an accessibility tab, if provided

My last official contribution to GitHub was something I’ve wanted for a long time: Writing the code to display an ACCESSIBILITY.md file’s contents on the repository landing page. This content lives in the same tab component that the README, License, Code of Conduct, Security, and important information is surfaced. For example, I’m using an ACESSIBILITY.md file located in ./github to communicate my accessibility statement on my a11y-webring.club repository. Here’s an image of it in action: The file only appears if it is supplied, so it is not a required part of creating or maintaining a repository. However, it is my hope that the act of providing one becomes more commonplace the same way providing those other special kinds of files are. Another broader hope I have is that this promotion of content helps to normalize accessibility as a consideration and practice in some small way—something that helps to send a signal of a mature software project. I’m excited to see how people use this new addition to the platform. I would also like to extend a huge thank you to Jan Maarten and Maria Lamardo for their help getting this effort across the finish line.

yesterday • 1 votes
Winner, Name that Ware August 2026

The Ware for August 2026 is the “IC unit” from a Lafayette 150-in-1 “IC Electronic Project Kit”, part number 99-35107. Above is a contextual photo of how the unit looked mounted in the kit. And above are a couple examples of projects you can build with the “IC” as part of the kit. Answering Hales’ […]

3 days ago • 1 votes
📚 BoredReading

You seem to be enjoying this.

Join free to unlock everything.

Create free account

Already have an account? Sign in