What is zero-copy I/O and how do sendfile/splice help?

A strong answer

A strong candidate frames What is zero-copy I/O and how do sendfile/splice help? around the exact memory layout, compiler semantics, and hardware execution model covered in Zero-Copy Data Pipelines: sendfile, splice, and Vectored I/O. Explain avoiding userspace copies by moving data between kernel buffers directly via sendfile, splice, and vectored I/O.

Serving files across a network is one of the most common tasks in systems programming: an HTTP server delivering an image, a video service streaming a media file, or a database streaming backup archives.

Trace what happens for every 8 KB chunk:

1. Context Switch 1 & 2 (read): The application traps into kernel mode. The disk controller uses Direct Memory Access (DMA) to copy the file block into the Kernel Page Cache (Copy 1). The CPU then copies the data from kernel page cache into user space buffer (Copy 2). The system call returns to user space.
2. Context Switch 3 & 4 (write): The application traps back into kernel mode. The CPU copies the data from user space buffer into the Kernel Socket Buffer (Copy 3). The system call returns to user space. Finally, the network card DMA engine pulls the data from the socket buffer to the physical wire (Copy 4).

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Stream disk files directly to network sockets using Linux sendfile.
• Mastery of core invariant: Transfer byte streams between arbitrary file descriptors and pipes via splice and tee.
• Mastery of core invariant: Batch non-contiguous memory buffers into atomic transmissions using writev and readv.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.