Lines Matching refs:and

4 Since 2.4.20 (and some versions before, with patches), and 2.5.45,
6 activity. Tools such as sar and iostat typically interpret these and do
12 places: one is in the file /proc/diskstats, and the other is within
16 Both /proc/diskstats and sysfs use the same source for the information
17 and so should not differ.
46 /proc/diskstats, the eleven fields will be preceded by the major and
47 minor device numbers, and device name.  Each of these formats provides
51 overflow and wrap).  Yes, these are (32-bit or 64-bit) unsigned long
52 (native word size) numbers, and on a very busy or long-lived system they
58 system-wide stats you'll have to find all the devices and sum them all up.
63     Reads and writes which are adjacent to each other may be merged for
65     ultimately handed to the disk, and so it will be counted (and queued)
83     given to appropriate struct request_queue and decremented as they finish.
91     I/O completion time and the backlog that may be accumulating.
103 summed to) and the result given to the user.  There is no convenient
109 There were significant changes between 2.4 and 2.6 in the I/O subsystem.
112 the host disk happens much earlier.  All merges and timings now happen
113 at the disk level rather than at both the disk and partition level as
129 Note that since the address is translated to a disk-relative one, and no
133 of queuing for partitions, and at completion for whole disks.  This is
137 reads/writes before merges for partitions and after for disks. Since a
138 typical workload usually contains a lot of successive and adjacent requests,
142 In 2.6.25, the full statistic set is again available for partitions and
143 disk and partition statistics are consistent again. Since we still don't
160 appear in both /proc/partitions and /proc/stat, although the ones in