freeblock-scheduling · research

Freeblock scheduling

Freeblock scheduling fits background HDD transfers into predicted rotational delays while aiming to preserve the next foreground transfer's timing.

Related Observatory article: Freeblock scheduling on hesela.com

The foreground request is selected first; background work uses the remaining positioning opportunity. Extra seeks consume some of that opportunity. This is not simply waiting until the request queue is empty. [1]

Large sets of unordered blocks give the scheduler more choices. The last blocks of a scan can be awkward to reach; promoting them to foreground priority trades scan completion against foreground interference. [1]

The FAST 2002 external prototype used limited command queueing and adjacent-request merging to handle timing and drive-cache behavior. Imperfect prediction and control reduced usable bandwidth relative to the earlier simulation. [2]

Relations

related
Rotational latency, I/O scheduler, Anticipatory scheduling, Data scrubbing

Limitations

  • Prediction errors can miss the intended sector passage and add a rotation of delay. [2]

Citations

  1. Lumb et al. Towards Higher Disk Head Utilization: Extracting "Free" Bandwidth from Busy Disk Drives. OSDI 2000, sections 2, 5.2 and 6. (accessed 2026-11-09)
  2. Lumb, Schindler and Ganger. Freeblock Scheduling Outside of Disk Firmware. FAST 2002, pp. 275-288; sections 2-5. (accessed 2026-11-09)

Further reading

  1. Hesela: HDD rotational slack versus waiting for demand (accessed 2026-11-09)
Sources & caveats
  • Historical source synthesis, not a current Linux scheduler option, SSD capability or reproduced benchmark.

JSON: /data/terms/freeblock-scheduling.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Freeblock scheduling. Hesela. 2026-11-09. https://hesela.dev/terms/freeblock-scheduling/