IOFlow
IOFlow is a research architecture that exposes storage-stage queues to a logically centralized controller for end-to-end I/O policies.
The controller maps high-level flows onto stage queues with service and routing controls. Storage tokens represent operation cost, not simply request-header bytes. [1]
Its Windows prototype inserts drivers around SMB stages without requiring application or VM changes. Requests already inside an uncontrolled device remain outside its priority decisions; limiting outstanding work retains more scheduling choice upstream. [1]
For evaluation, name the enforcement stage, operation-cost model and outstanding-request boundary. A configured rate alone does not establish application tail latency.
Relations
- related
- sRoute, I/O scheduler, mClock, Queue depth
Advantages
- A controller can coordinate policies across several storage stages. [1]
Limitations
- Priority enforcement depends on where contention occurs and which stages expose control. [1]
Citations
Sources & caveats
- Primary-paper architecture review; no prototype execution or contemporary performance measurement.