1The I/O bandwidth controller testplan includes a complete set of testcases to 2verify the effectiveness of the block device I/O throttling capabilities for 3cgroups. 4 5I/O bandwidth limitations are imposed by the testcase script and verified doing 6I/O activity on a limited block device. Tests are supposed to be passed if the 7I/O rates of all the different workloads always respect the I/O limitations. 8 9TESTCASE DESCRIPTION: 10==================== 11First of all we evaluate the physical I/O bandwidth (physical-io-bw) of the 12block device where the current working directory resides. 13 14Based on the physical I/O bandwidth three cgroups are created: cgroup-1, 15cgroup-2, cgroup-3. Cgroups use respectively the following I/O bandwidth 16limitations: 17- cgroup-1: physical-io-bw / 2 18- cgroup-2: physical-io-bw / 4 19- cgroup-3: physical-io-bw / 8 20 21Each test is considered passed only if the I/O limitations above are respected. 22 23Currently the following different scenarios are tested: 24- 1 single stream per cgroup using leaky-bucket I/O throttling 25- 1 single stream per cgroup using token-bucket I/O throttling 26- 2 parallel streams per cgroup using leaky-bucket I/O throttling 27- 2 parallel streams per cgroup using token-bucket I/O throttling 28- 4 parallel streams per cgroup using leaky-bucket I/O throttling 29- 4 parallel streams per cgroup using token-bucket I/O throttling 30 31For any other information please refer to 32Documentation/controllers/io-throttle.txt in kernel documentation. 33 34Questions? 35---------- 36Send email to: righi.andrea@gmail.com 37