Ac Low Level Io And Syscalls

The boundary between a program and the kernel: syscall cost and batching, buffered versus direct I/O, memory-mapped files and when they beat read, epoll and readiness-based event loops, io_uring and submission queues, vectored I/O, blocking versus non-blocking sockets, and the written I/O record. It explains what crossing the kernel boundary costs and how to cross it fewer times; it never recommends a framework and never promises a throughput. Use when asking "syscall overhead", "read vs mmap", "direct I/O", "epoll", "io_uring", "zero copy", "sendfile", "vectored I/O", "blocking versus non-blocking", "why is reading this file slow", "batching syscalls". Not for application caching (ac-caching-and-invalidation), not for distributed replication (ac-distributed-state-and-replication), not for file format layout (ac-binary-formats).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit bddfcc383b

Frequently asked questions

npx get-skill add jiayaoqijia/ac-low-level-io-and-syscalls