Features/DiskIOLimits: Difference between revisions
(Created page with '== Summary == Provide interfaces to throttle disk I/O independent of the underlying storage (image file, LVM, NFS, Ceph). == Owners == * '''Name:''' Zhi Yong WU * '''Email:'''…') |
(→Owners) |
||
| Line 7: | Line 7: | ||
* '''Name:''' Zhi Yong WU | * '''Name:''' Zhi Yong WU | ||
* '''Email:''' zwu@linux.vnet.ibm.com | * '''Email:''' zwu@linux.vnet.ibm.com | ||
== Status == | == Status == | ||
Revision as of 10:08, 24 May 2011
Summary
Provide interfaces to throttle disk I/O independent of the underlying storage (image file, LVM, NFS, Ceph).
Owners
- Name: Zhi Yong WU
- Email: zwu@linux.vnet.ibm.com
Status
Planning - this feature has not yet been widely discussed or implemented.
Background
When several instances of QEMU are running they can interfere with system performance through excessive disk I/O. Sometimes it is desirable to limit disk I/O in order to keep QEMU from affecting other applications or instances.
The availability of disk I/O throttling depends on the underlying storage (image file, LVM, NFS, Ceph). On Linux the cgroups blkio-controller supports I/O throttling on block devices but is a relatively recent feature. More importantly, there is no single mechanism for disk I/O throttling across all underlying storage types and for some types there is no way to throttle at all.
The disk I/O limits feature introduces QEMU block layer I/O limits together with command-line and QMP interfaces for configuring limits. This allows I/O limits to be imposed across all underlying storage types using a single interface.