Lines Matching +full:system +full:- +full:trace

1 .TH fileslower 8  "2016-02-07" "USER COMMANDS"
3 fileslower \- Trace slow synchronous file reads and writes.
5 .B fileslower [\-h] [\-p PID] [-a] [min_ms]
9 system.
14 system request types: file reads and writes. There are typically many others:
30 \-p PID
31 Trace this PID only.
33 \-a
34 Include non-regular file types in output (sockets, FIFOs, etc).
37 Minimum I/O latency (duration) to trace, in milliseconds. Default is 10 ms.
40 Trace synchronous file reads and writes slower than 10 ms:
44 Trace slower than 1 ms:
48 Trace slower than 1 ms, for PID 181 only:
50 .B fileslower \-p 181 1
70 to when it completed. This time is inclusive of block device I/O, file system
71 CPU cycles, file system locks, run queue latency, etc. It's a more accurate
72 measure of the latency suffered by applications performing file system I/O,
76 A cached kernel file name (comes from dentry->d_name.name).
81 often at the lower end of the spectrum -- test before use. The reason for
85 and uses in-kernel eBPF maps for efficient timing and filtering, multiply that
90 # ./funccount.py -i 1 -r '^__vfs_(read|write)$'
95 down-stack a little from VFS into the file system functions (ext4, xfs, etc).
96 Look for updates to bcc for specific file system tools that do this. The
97 advantage of a per-file system approach is that we can trace post-cache,
99 tracing approaches for each different file system (whereas VFS is generic).
110 Unstable - in development.