All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: axboe@kernel.dk
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Documentation/cgroups/blkio-controller.txt: s/disk_time|disk_sectors/time|sectors/
Date: Sat, 17 Nov 2012 17:17:48 +0800	[thread overview]
Message-ID: <50A7563C.4040404@oracle.com> (raw)

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@oracle.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

                 reply	other threads:[~2012-11-17  9:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50A7563C.4040404@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.