For adults only (18+)
© Staxus.com, 2026 RTA
Hardware is asynchronous. The disk finishes reading. The network card receives a packet. The keyboard is pressed. The kernel must respond to these events in microseconds.
The kernel, with the help of the CPU’s Memory Management Unit (MMU), maintains page tables. These are maps that translate a process’s fake “virtual address” into a real “physical address.” When a process touches a memory location that isn’t mapped— page fault —the kernel wakes up. It might load data from disk (swap), allocate a new physical page, or, if the access was illegal, kill the process with the infamous SIGSEGV (Segmentation Fault). what is os kernel
The kernel is not really software. It is a . Hardware is asynchronous
The CPU does not know what a “file” is. It does not know what a “network socket” is. It does not know that you have a right to privacy, that two programs shouldn’t write to the same memory location, or that time should be shared fairly among a hundred running tasks. The CPU is a breathtakingly fast idiot, capable only of fetching an instruction, decoding it, executing it, and moving to the next address. The keyboard is pressed
The kernel is the that makes civilization possible on top of this idiot. The Privilege Ring: The Kernel as High Priest At the hardware level, the kernel is defined by a single, critical concept: privilege . Modern CPUs have at least two modes: user mode and kernel mode (often called "ring 3" and "ring 0"). In user mode, the CPU is handcuffed. It cannot talk directly to hardware. It cannot manage memory pages. It cannot halt the system. It can only ask the kernel for permission.
Physical RAM is a messy, fragmented, limited resource. The kernel hides this horror with virtual memory . Every process believes it owns the entire address space, from address 0 to 2^64. This is a lie.