Important Terms in Operating Systems

Important terms in operating systems are the kernel, multiprogramming, multitasking, spooling and interrupt. The kernel is the privileged core managing the CPU, memory and devices, multiprogramming keeps several programs in memory so the CPU stays busy, multitasking switches between them in time slices, spooling buffers output for slow devices, and an interrupt pauses the CPU to run a handler.

4 min read

Several OS terms get used constantly across every other topic in this subject, scheduling, memory management, synchronization, all assume you already know exactly what these words mean. Getting them precisely right early saves confusion everywhere else.

Kernel

The kernel is the core part of the operating system that runs with full hardware privileges (kernel mode), directly managing the CPU, memory, and devices. Everything else commonly bundled under "the operating system", command-line tools, a graphical desktop, bundled applications, runs in restricted user mode and asks the kernel to do privileged work via system calls. When people distinguish "Linux" (the kernel) from "a Linux distribution" like Ubuntu (kernel plus a huge collection of user-mode software built around it), this is exactly the line they're drawing.

Multiprogramming

Multiprogramming means keeping multiple programs loaded in memory at once, so that when one program is waiting on something slow (disk I/O, network), the CPU switches to running a different program instead of sitting idle. The goal is maximizing CPU utilization: keep the expensive processor busy with useful work instead of waiting around for slow I/O to finish.

Multitasking

Multitasking builds on multiprogramming by rapidly switching the CPU between multiple programs in small time slices, giving the appearance that they're running simultaneously (even on a single CPU core). The goal shifts from pure CPU utilization toward responsiveness: a user interacting with multiple applications at once should feel like each one is live and reactive, not queued up waiting its turn.

Spooling

Spooling (Simultaneous Peripheral Operations On-Line) is the technique of writing output destined for a slow device (classically a printer) to a fast intermediate storage area first, then letting the slow device consume from that buffer at its own pace, while the program that generated the output keeps running immediately instead of blocking until the slow device finishes. A modern print queue, where you send several documents to print and keep working immediately while they print one after another in the background, is spooling in action.

Interrupt

An interrupt is a signal sent to the CPU, either by hardware (a key was pressed, a network packet arrived) or software (a program executed a special instruction), that pauses whatever the CPU is currently doing so it can immediately run a specific handler routine for that event, then resume the original work afterward. Interrupts are the mechanism that lets a CPU respond immediately to events instead of having to constantly poll every device in a loop asking "did anything happen yet?"

Where this matters in real systems

Every modern general-purpose OS, Linux, Windows, macOS, relies on all five of these concepts simultaneously and continuously: the kernel is running right now managing your hardware, multiprogramming and multitasking are why your background music player and foreground browser both feel responsive, your OS's print subsystem still uses a literal spooler, and every keystroke you make reaches your application via a hardware interrupt, not the CPU constantly checking the keyboard in a loop.

What interviewers actually ask about these terms

  • "What's the difference between multiprogramming and multitasking?" Multiprogramming keeps multiple programs in memory to maximize CPU utilization when one is blocked on I/O; multitasking rapidly switches between programs to create the appearance of simultaneous, responsive execution.
  • "What is a kernel, and how is it different from 'the operating system'?" The kernel is the privileged core managing hardware directly; "operating system" often refers to the kernel plus the surrounding user-mode tools and services bundled with it.
  • "What is spooling, and why does it help?" Buffering output for a slow device in fast intermediate storage, so the program producing that output can continue immediately instead of blocking until the slow device finishes.
  • "What is an interrupt, and why not just poll devices in a loop instead?" A signal that immediately pauses the CPU to handle an event; polling would waste CPU cycles constantly checking devices that usually have nothing new to report, interrupts let the CPU do other work until something genuinely happens.

Key takeaways

  • The kernel is the OS's privileged core; "operating system" usually means kernel plus bundled user-mode tools.
  • Multiprogramming maximizes CPU utilization by keeping several programs ready to run when one blocks on I/O.
  • Multitasking rapidly switches between programs to simulate simultaneous, responsive execution.
  • Spooling buffers output for a slow device so the producing program isn't blocked waiting on it.
  • Interrupts let the CPU react immediately to hardware or software events instead of constantly polling for them.
All 205 OS interview questions

Browse all Operating Systems topics

Log in to save which topics you've read across every subject.

Frequently asked questions

What's the difference between multiprogramming and multitasking?

Multiprogramming keeps multiple programs in memory to maximize CPU utilization when one is blocked on I/O; multitasking rapidly switches between programs to create the appearance of simultaneous, responsive execution.

What is a kernel, and how is it different from 'the operating system'?

The kernel is the privileged core managing hardware directly; "operating system" often refers to the kernel plus the surrounding user-mode tools and services bundled with it.

What is spooling, and why does it help?

Buffering output for a slow device in fast intermediate storage, so the program producing that output can continue immediately instead of blocking until the slow device finishes.

What is an interrupt, and why not just poll devices in a loop instead?

A signal that immediately pauses the CPU to handle an event; polling would waste CPU cycles constantly checking devices that usually have nothing new to report, interrupts let the CPU do other work until something genuinely happens.