A from-first-principles walk through how I/O actually works in C. We start with what I/O really is and the wall between your program and the kernel, then look at what every read() and write() actually costs — the mode switch, the buffer copy, the cache pollution. From there we write the simplest blocking server, see why it can only serve one client at a time, and try to fix it with further approaches.
#systemsprogramming #linux #c #networking #unix #lowlevel #epoll