Skip to content

Commit 77fe428

Browse files
seeekryonghong-song
authored andcommitted
fix typos in tutorial.md (iovisor#2584)
fix typos in tutorial.md
1 parent d8381fb commit 77fe428

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ TIME COMM PID T BYTES OFF_KB LAT(ms) FILENAME
9797

9898
ext4slower traces the ext4 file system and times common operations, and then only prints those that exceed a threshold.
9999

100-
This is great for identifying or exonerating one type of performance issue: slow individually slow disk i/O via the file system. Disks process I/O asynchronously, and it can be difficult to associate latency at that layer with the latency applications experience. Tracing higher up in the kernel stack, at the VFS -> file system interface, will more closely match what an application suffers. Use this tool to identify if file system latency exceeds a given threshold.
100+
This is great for identifying or exonerating one type of performance issue: show individually slow disk i/O via the file system. Disks process I/O asynchronously, and it can be difficult to associate latency at that layer with the latency applications experience. Tracing higher up in the kernel stack, at the VFS -> file system interface, will more closely match what an application suffers. Use this tool to identify if file system latency exceeds a given threshold.
101101

102102
Similar tools exist in bcc for other file systems: btrfsslower, xfsslower, and zfsslower. There is also fileslower, which works at the VFS layer and traces everything (although at some higher overhead).
103103

@@ -151,7 +151,7 @@ TIME(s) COMM PID DISK T SECTOR BYTES LAT(ms)
151151

152152
biosnoop prints a line of output for each disk I/O, with details including latency (time from device issue to completion).
153153

154-
This allows you to examine disk I/O in more detail, and look for time-ordered patterns (eg, reads queueing behind writes). Note that the output will be verbose if your system performance a high rate of disk I/O.
154+
This allows you to examine disk I/O in more detail, and look for time-ordered patterns (eg, reads queueing behind writes). Note that the output will be verbose if your system performs disk I/O at a high rate.
155155

156156
More [examples](../tools/biosnoop_example.txt).
157157

0 commit comments

Comments
 (0)