Lines Matching refs:disk

12 The output is disk events - I/O operations that cause the disk to physically
15 physical disk events.
18 driver before disk events happen. disk events. The stack goes like this,
38        disk
40 Due to caching (after vfs) few events will make it to the disk for iosnoop
53 elapsed time from the disk request (strategy) to the disk completion
54 iodone); -o prints the time for the disk to complete that event
61 disk to complete the request, after it has travelled through any bus or
68    on your application's PID. You notice large times for the disk events
72    the disks at the same time, and is causing the disk heads to seek to
73    elsewhere on the disk surface - increasing both service and response time.
79 queue are reshuffeled to promote "elevator seeking" of the disk heads (this
80 reduces head seeking). So the time for a disk event can be effected not
85 fetch disk event data on a live system, the bad news is that understanding
88 For further information on disk measurements see,