Syscall

ELI5 - The Vibe Check

A syscall is your program raising its hand and asking the operating system kernel to do something it isn't allowed to do itself, like reading a file, opening a network connection, or allocating memory. Your program can't touch hardware directly for safety reasons, so it has to ask the kernel to do it on its behalf, and that ask-and-wait round trip isn't free, it's one of the reasons doing less I/O is such a common performance tip.

Real Talk

A system call (syscall) is a controlled entry point that lets a user-space program request a service from the operating system kernel, such as file I/O, memory allocation, or process management, since user-space code doesn't have direct hardware access. Each syscall involves a context switch into kernel mode and back, which carries measurable overhead, so I/O-heavy programs often try to batch or reduce the number of syscalls they make.

When You'll Hear This

"strace showed thousands of tiny read syscalls, that's why it's slow." / "Batching those writes cut our syscall count by 90%."