Prev: [PATCH 0/2] perf: perf_arch_fetch_regs_caller API change
Next: [PATCH 3/4] io-controller: a new interface to keep track of io rate when group is backlogged
From: Gui Jianfeng on 21 May 2010 04:50 Document for active bytes time and rate. Signed-off-by: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com> --- Documentation/cgroups/blkio-controller.txt | 21 +++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) diff --git a/Documentation/cgroups/blkio-controller.txt b/Documentation/cgroups/blkio-controller.txt index 48e0b21..2b015e8 100644 --- a/Documentation/cgroups/blkio-controller.txt +++ b/Documentation/cgroups/blkio-controller.txt @@ -168,6 +168,27 @@ Details of cgroup files cgroup. This is further divided by the type of operation - read or write, sync or async. +- blkio.io_active_bytes + - Total number bytes transferred to/from the disk by the group since + the group got backlogged. First two fields specify the major and + minor number of the device, the third field specifies the operation + type and the fourth field specifies the number of bytes. It will be + reset when group gets dequeued from service tree. + +- blkio.io_active_time + - Total amount of time(in ms) spent since the group got backlogged. + First two fields specify the major and minor number of the device, + third field specify how long it spents since the group got + backlogged. It will be reset when group gets enqueued onto service + tree. + +- blkio.io_active_rate + - The io rate (in bytes/ms) of the group when group is issuing io. + First two fields specify the major and minor number of the device, + the third field specifies the operation type and the fourth field + specifies the io rate. If there isn't any io on the group, io rate + won't be computed. + - blkio.avg_queue_size - Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y. The average queue size for this cgroup over the entire time of this -- 1.5.4.rc3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |