GateAI

GATE CSE CPU and I/O Scheduling PYQs

Medium yield21.9% of Operating Systems

CPU and I/O scheduling in GATE CS is predominantly an algorithmic and numerical topic focusing on precise Gantt chart simulation, turnaround/waiting time comput… Read the guide

Questions
25
Asked
since 2011
Total marks
42
Marks / paper
1.7

25 GATE CSE CPU and I/O Scheduling PYQs with solutions, from Operating Systems. Browse all GATE CSE PYQs.

Questions

Every official paper that asked this topic, newest first.

What GATE tests in CPU and I/O Scheduling

Concepts, patterns, formulas and traps distilled from past papers.

CPU and I/O scheduling in GATE CS is predominantly an algorithmic and numerical topic focusing on precise Gantt chart simulation, turnaround/waiting time computation, and comparative metric evaluation. While Preemptive Shortest Remaining Time First (SRTF) and Round Robin (RR) form the core of numerical problems, questions also assess real-time scheduling (Rate Monotonic), multi-processor scheduling, disk I/O head movement algorithms (SCAN, SSTF, C-LOOK), and theoretical properties like starvation and preemption hardware requirements.

Core concepts

  • Preemptive vs Non-Preemptive scheduling mechanics (SRTF vs SJF, Priority)
  • Round Robin queue management (tie-breaking at arrival vs quantum expiry)
  • Gantt chart construction with variable arrival times
  • Real-time Rate Monotonic Scheduling (RMS) with periodic tasks
  • Multi-processor / Dual-core task allocation under asymmetric priorities
  • Interleaved CPU burst and I/O burst execution pipelines
  • Disk seek scheduling policies (SSTF, SCAN, LOOK, C-SCAN, C-LOOK)
  • Starvation conditions, aging techniques, and convoy effect
  • Hardware prerequisites for preemption (programmable interval timer interrupts)

Recurring question patterns

  • Preemptive SRTF / Priority Metric Calculation

    CommonNAT2 marks2025, 2024, 2017, 2016

    A table of 3 to 5 processes with arrival times, burst times (and optional priorities) is given. Candidates must construct a precise Gantt chart tracking preemptions at arrival instants and compute average turnaround time or average waiting time.

  • Round Robin Execution & State/Switch Tracking

    Commonmixed2 marks2022, 2020, 2014, 2012

    Simulating Round Robin with a given time quantum qq, either determining completion orders, evaluating interleaved CPU-I/O bursts, tracing context switch pairs between specific processes, or comparing TAT/WT against SJF.

  • Comparative Algorithm Evaluation & Optimization

    Commonmixed2 marks2024, 2021, 2020, 2016

    Comparing metrics (average TAT, average WT, or head movement) across two or more algorithms (e.g., SRTF vs NP-SJF, SSTF vs SCAN, SJF vs RR) or identifying optimal scheduling properties.

  • Disk I/O Head Scheduling

    OccasionalNAT2 marks2016, 2015

    Given a sequence of cylinder/track requests, initial head position, and direction, calculate total seek distance or seek distance differences using SSTF, SCAN, LOOK, C-SCAN, or C-LOOK.

  • Advanced / Non-Standard Scheduling Models

    Occasionalmixed2 marks2026, 2025, 2015, 2013

    Novel variations such as Rate Monotonic periodic task deadlines, dynamic priority re-evaluation over time, interleaved arrivals of multiple process streams, or multi-processor scheduling with asymmetric priority lists.

  • Conceptual & MSQ Theoretical Properties

    OccasionalMSQ1 marks2026, 2023, 2021, 2013

    Testing theoretical definitions and boundary cases: starvation vulnerability, preemption hardware dependencies (timer interrupt), metric definitions (TAT = WT + BT), or algorithm equivalence.

Formulas GATE uses

Turnaround Time (TAT)

TAT=Completion Time (CT)−Arrival Time (AT)\text{TAT} = \text{Completion Time (CT)} - \text{Arrival Time (AT)}

Used in virtually all CPU scheduling Gantt chart calculations to find process turnaround duration.

Waiting Time (WT)

WT=TAT−Burst Time (BT)\text{WT} = \text{TAT} - \text{Burst Time (BT)}

Used to find total wait time in ready queue for CPU-bound processes.

Average Metric Calculation

Avg X=∑i=1nXin\text{Avg } X = \frac{\sum_{i=1}^{n} X_i}{n}

Used to compute average waiting time or average turnaround time across all nn processes.

Rate Monotonic Priority Rule

Priority∝1Pi\text{Priority} \propto \frac{1}{P_i}

Used when periodic real-time tasks are scheduled with priority inversely proportional to task period PiP_i.

C-LOOK Total Head Movement

Total Seek=(MaxReq−StartPos)+(MaxReq−MinReq)+(LastReq−MinReq)\text{Total Seek} = (\text{MaxReq} - \text{StartPos}) + (\text{MaxReq} - \text{MinReq}) + (\text{LastReq} - \text{MinReq})

Used for C-LOOK disk scheduling moving upwards to the maximum request then wrapping to the minimum request.

Examiner traps in CPU and I/O Scheduling

  • Ready Queue order on concurrent events: When a process quantum expires at the exact instant a new process arrives, failing to put the newly arrived process ahead of or behind the preempted process according to specified rules.
  • Subtracting Arrival Time: Forgetting to subtract Arrival Time when computing Turnaround Time (confusing Completion Time with TAT when AT > 0).
  • Waiting Time in Preemption: Calculating waiting time merely as first start time minus arrival time, which fails when a process is preempted multiple times.
  • Disk boundary traversal: Confusing SCAN (which travels all the way to track 0 or track Max) with LOOK (which stops at the extreme request), or C-SCAN vs C-LOOK.
  • SSTF tie-breaking: Moving in the wrong direction when two track requests are equidistant from the current head position.
  • Multi-core contention: Assigning a newly freed processor without checking if a higher-priority process is already running on another core or queued with specific processor affinity.

How questions are asked

  • Compute average waiting time or turnaround time from a process table (NAT/MCQ)
  • Identify execution/completion order of processes across two algorithms (MCQ)
  • Compute total disk head movements or delta between two disk algorithms (NAT)
  • Trace context switch transitions or determine valid/invalid burst time configurations (MCQ)
  • Multi-statement correctness on scheduling properties and starvation (MSQ)
  • Multi-processor / real-time multi-task periodic completion time calculation (NAT/MCQ)

Paper trends

  • Shift from simple single-algorithm MCQ questions to multi-algorithm comparison questions and precise NAT numerical outputs.

    2024, 2020, 2016, 2014, 2011

  • Introduction of multi-processor asymmetric scheduling rules and complex multi-stream interleaved arrival workloads.

    2026, 2025

  • Use of MSQs to test nuanced conceptual foundations such as starvation edge cases and hardware support requirements for preemption.

    2023, 2021

Difficulty notes

Easy: Single-algorithm standard metrics with identical arrival times (t=0t=0) or pure definitional MSQ/MCQ questions. Medium: SRTF/RR with 4-5 processes, staggered arrival times, context-switch tracking, or disk head calculations. Hard: Multi-core scheduling with asymmetric priority constraints, multi-loop CPU-I/O pipelines, or inverse reasoning to deduce impossible burst configurations from switch sequences.