Lines Matching full: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 15 fields of statistics, each meaning exactly the same things.
57 it. Regarding wrapping, the types of the fields are either unsigned
62 Each set of stats only applies to the indicated device; if you want
65 Field 1 -- # of reads completed (unsigned long)
66 This is the total number of reads completed successfully.
68 Field 2 -- # of reads merged, field 6 -- # of writes merged (unsigned long)
74 Field 3 -- # of sectors read (unsigned long)
75 This is the total number of sectors read successfully.
77 Field 4 -- # of milliseconds spent reading (unsigned int)
78 This is the total number of milliseconds spent by all reads (as
81 Field 5 -- # of writes completed (unsigned long)
82 This is the total number of writes completed successfully.
84 Field 6 -- # of writes merged (unsigned long)
85 See the description of field 2.
87 Field 7 -- # of sectors written (unsigned long)
88 This is the total number of sectors written successfully.
90 Field 8 -- # of milliseconds spent writing (unsigned int)
91 This is the total number of milliseconds spent by all writes (as
94 Field 9 -- # of I/Os currently in progress (unsigned int)
98 Field 10 -- # of milliseconds spent doing I/Os (unsigned int)
103 I/O time might be not accounted in case of concurrent requests.
105 Field 11 -- weighted # of milliseconds spent doing I/Os (unsigned int)
107 merge, or read of these stats by the number of I/Os in progress
108 (field 9) times the number of milliseconds spent doing I/O since the
109 last update of this field. This can provide an easy measure of both
112 Field 12 -- # of discards completed (unsigned long)
113 This is the total number of discards completed successfully.
115 Field 13 -- # of discards merged (unsigned long)
116 See the description of field 2
118 Field 14 -- # of sectors discarded (unsigned long)
119 This is the total number of sectors discarded successfully.
121 Field 15 -- # of milliseconds spent discarding (unsigned int)
122 This is the total number of milliseconds spent by all discards (as
125 Field 16 -- # of flush requests completed
126 This is the total number of flush requests completed successfully.
131 Field 17 -- # of milliseconds spent flushing
132 This is the total number of milliseconds spent by all flush requests.
138 but due to the lack of locking it may only be very close.
140 In 2.6+, there are counters for each CPU, which make the lack of locking
161 Field 1 -- # of reads issued
162 This is the total number of reads issued to this partition.
164 Field 2 -- # of sectors read
165 This is the total number of sectors requested to be read from this
168 Field 3 -- # of writes issued
169 This is the total number of writes issued to this partition.
171 Field 4 -- # of sectors written
172 This is the total number of sectors requested to be written to
176 record of the partition-relative address is kept, the subsequent success
177 or failure of the read cannot be attributed to the partition. In other
178 words, the number of reads for partitions is counted slightly before time
179 of queuing for partitions, and at completion for whole disks. This is
182 More significant is the error induced by counting the numbers of
184 typical workload usually contains a lot of successive and adjacent requests,
185 the number of reads/writes issued can be several times higher than the
186 number of reads/writes completed.
190 keep record of the partition-relative address, an operation is attributed to
191 the partition which contains the first sector of the request after the
198 In 2.6+, sysfs is not mounted by default. If your distribution of