Lines Matching refs:of
16 is mounted on ``/sys``, although of course it may be mounted anywhere.
20 Here are examples of these different formats::
38 a choice of ``cat /sys/block/hda/stat`` or ``grep 'hda ' /proc/diskstats``.
40 The advantage of one over the other is that the sysfs choice works well
41 if you are watching a known, small set of disks. ``/proc/diskstats`` may
42 be a better choice if you are watching a large number of disks because
43 you'll avoid the overhead of 50, 100, or 500 or more opens/closes with
44 each snapshot of your disk statistics.
47 the above example, the first field of statistics would be 446216.
51 minor device numbers, and device name. Each of these formats provides
52 eleven fields of statistics, each meaning exactly the same things.
58 your observations are measured in large numbers of minutes or hours,
61 Each set of stats only applies to the indicated device; if you want
64 Field 1 -- # of reads completed
65 This is the total number of reads completed successfully.
67 Field 2 -- # of reads merged, field 6 -- # of writes merged
73 Field 3 -- # of sectors read
74 This is the total number of sectors read successfully.
76 Field 4 -- # of milliseconds spent reading
77 This is the total number of milliseconds spent by all reads (as
80 Field 5 -- # of writes completed
81 This is the total number of writes completed successfully.
83 Field 6 -- # of writes merged
84 See the description of field 2.
86 Field 7 -- # of sectors written
87 This is the total number of sectors written successfully.
89 Field 8 -- # of milliseconds spent writing
90 This is the total number of milliseconds spent by all writes (as
93 Field 9 -- # of I/Os currently in progress
97 Field 10 -- # of milliseconds spent doing I/Os
100 Field 11 -- weighted # of milliseconds spent doing I/Os
102 merge, or read of these stats by the number of I/Os in progress
103 (field 9) times the number of milliseconds spent doing I/O since the
104 last update of this field. This can provide an easy measure of both
107 Field 12 -- # of discards completed
108 This is the total number of discards completed successfully.
110 Field 13 -- # of discards merged
111 See the description of field 2
113 Field 14 -- # of sectors discarded
114 This is the total number of sectors discarded successfully.
116 Field 15 -- # of milliseconds spent discarding
117 This is the total number of milliseconds spent by all discards (as
124 but due to the lack of locking it may only be very close.
126 In 2.6+, there are counters for each CPU, which make the lack of locking
144 Field 1 -- # of reads issued
145 This is the total number of reads issued to this partition.
147 Field 2 -- # of sectors read
148 This is the total number of sectors requested to be read from this
151 Field 3 -- # of writes issued
152 This is the total number of writes issued to this partition.
154 Field 4 -- # of sectors written
155 This is the total number of sectors requested to be written to
159 record of the partition-relative address is kept, the subsequent success
160 or failure of the read cannot be attributed to the partition. In other
161 words, the number of reads for partitions is counted slightly before time
162 of queuing for partitions, and at completion for whole disks. This is
165 More significant is the error induced by counting the numbers of
167 typical workload usually contains a lot of successive and adjacent requests,
168 the number of reads/writes issued can be several times higher than the
169 number of reads/writes completed.
173 keep record of the partition-relative address, an operation is attributed to
174 the partition which contains the first sector of the request after the
181 In 2.6+, sysfs is not mounted by default. If your distribution of