dm-ioband
Overview
dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. If you use dm-ioband with blkio-cgroup (described below), you can also control bandwidth on per cgroup basis.
dm-ioband distributes bandwidth to each group (group is determined by partition, user ID, process ID and so on) according to bandwidth control policies. Currently, dm-ioband supports three kinds of policies:
- weight policy
- This policy distributes bandwidth proportional to the weight of each group and charges to each group on an I/O count basis. If there are some groups that are inactive, other active groups can use the spare bandwidth of those inactive groups.
- weight-iosize policy
- Same as "weight" policy, but it charges on an I/O size basis.
- range-bw policy
- range-bw means the predicable I/O bandwidth with minimum and maximum value defined by administrator. And it is also possible to set up only maximum value for only I/O limitation. So, you can define the specific and fixed bandwidth to satisfy I/O requirement regardless of whole I/O bandwidth.
Download
- Binary packages for RHEL5.x and CentOS 5.x
- RPM binary packages are for Red Hat Enterprise Linux 5.x and CentOS 5.x. They were tested on RHEL 5.3 and CentOS 5.3 and will also work on other 5.x versions.
- dm-ioband-config package
- The dm-ioband-config package provides a configuration file and an init script to make it easy to assign bandwidth to LVM logical volumes.
Documentation
- Online manual
- Benchmark results
-
- Benchmarks in a variety of configurations
- Benchmarks with a high performance storage system
- Test Report
- dm-ioband Test Report (Required OpenOffice? Calc)
I'm waiting for your comments and ideas on the device-mapper mailing list dm-devel@….
For more information about this list, please refer to Device-mapper Resource Page .
Attachments
- test-report.xls (72.0 KB) - added by ryov 3 years ago.