linux-kernel - [PATCH] Documentation/cgroups/blkio-controller.txt: s/disk_time|disk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 17 Nov 2012 17:17:48 +0800
From:	Jeff Liu <jeff.liu@...cle.com>
To:	axboe@...nel.dk
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH] Documentation/cgroups/blkio-controller.txt: s/disk_time|disk_sectors/time|sectors/

Hello,

For blkio controller of cgroup, both disk_time and disk_sectors were
obsolated file names.  Now we're using blkio.time and blkio.sectors to
examine how much disk time each cgroup got and how many sectors each
cgroup dispatched separately.

This patch fix the document to reflect those changes as well as a couple
of typos(secotors and io.disk_time).

Thanks,
-Jeff


Signed-off-by: Jie Liu <jeff.liu@...cle.com>

---
 Documentation/cgroups/blkio-controller.txt |   14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/cgroups/blkio-controller.txt b/Documentation/cgroups/blkio-controller.txt
index b4b1fb3..ffa26d1 100644
--- a/Documentation/cgroups/blkio-controller.txt
+++ b/Documentation/cgroups/blkio-controller.txt
@@ -57,11 +57,11 @@ cgroups. Here is what you can do.
 	cat /sys/fs/cgroup/blkio/test2/tasks
 
 - At macro level, first dd should finish first. To get more precise data, keep
-  on looking at (with the help of script), at blkio.disk_time and
-  blkio.disk_sectors files of both test1 and test2 groups. This will tell how
-  much disk time (in milli seconds), each group got and how many secotors each
-  group dispatched to the disk. We provide fairness in terms of disk time, so
-  ideally io.disk_time of cgroups should be in proportion to the weight.
+  on looking at (with the help of script), at blkio.time and blkio.sectors files
+  of both test1 and test2 groups. This will tell how much disk time (in milli
+  seconds), each group got and how many sectors each group dispatched to the disk.
+  We provide fairness in terms of disk time, so ideally blkio.time of cgroups
+  should be in proportion to the weight.
 
 Throttling/Upper Limit policy
 -----------------------------
@@ -84,8 +84,8 @@ Throttling/Upper Limit policy
 
 - Run dd to read a file and see if rate is throttled to 1MB/s or not.
 
-		# dd if=/mnt/common/zerofile of=/dev/null bs=4K count=1024
-		# iflag=direct
+	# dd if=/mnt/common/zerofile of=/dev/null bs=4K count=1024
+	# iflag=direct
         1024+0 records in
         1024+0 records out
         4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s
-- 
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/