0 views collected around this technical thread.
This article breaks down zero‑copy data transfer techniques—write+read, mmap+write, sendfile, sendfile + SG‑DMA, and splice—showing how they reduce CPU copies and context switches to boost I/O performance in modern operating systems.
This article explains the concept of zero‑copy in Linux, compares the four main system calls—sendfile, mmap, splice and tee—describes their APIs, internal mechanisms, performance characteristics, typical use‑cases and provides practical code examples for high‑performance network programming.
This article explains how zero‑copy techniques such as mmap, sendfile, and splice reduce CPU involvement in data transfer by avoiding memory copies between kernel and user spaces, and shows how Java NIO and Netty implement these mechanisms for high‑performance backend I/O.
FUSE implements a user‑space file‑system framework where a kernel module creates the /dev/fuse device and forwards VFS requests into kernel queues, while a multi‑threaded daemon reads these requests, optionally uses splice for zero‑copy, processes them, and writes replies back, enabling simple file‑system development without kernel recompilation.