Searched full:funccount (Results 1 – 25 of 34) sorted by relevance
12
| /external/bcc/tools/ |
| D | funccount_example.txt | 1 Demonstrations of funccount, the Linux eBPF/bcc version.
8 # ./funccount 'vfs_*'
35 # ./funccount 'tcp_*'
172 # ./funccount -p 1442 /home/ubuntu/contentions:*
185 # ./funccount -p 1442 contentions:*
190 # ./funccount -r 'c:(write|read)$'
202 # ./funccount t:block:*
216 # ./funccount u:pthread:*mutex* -p 1442
229 # ./funccount -i 1 'vfs_*'
272 # ./funccount -i 1 -d 5 vfs_read
[all …]
|
| D | funccount.py | 4 # funccount Count functions, tracepoints, and USDT probes.
7 # USAGE: funccount [-h] [-p PID] [-i INTERVAL] [-d DURATION] [-T] [-r] pattern
216 ./funccount 'vfs_*' # count kernel fns starting with "vfs"
217 ./funccount -r '^vfs.*' # same as above, using regular expressions
218 ./funccount -Ti 5 'vfs_*' # output every 5 seconds, with timestamps
219 ./funccount -d 10 'vfs_*' # trace for 10 seconds only
220 ./funccount -p 185 'vfs_*' # count vfs calls for PID 181 only
221 ./funccount t:sched:sched_fork # count calls to the sched_fork tracepoint
222 ./funccount -p 185 u:node:gc* # count all GC USDT probes in node, PID 185
223 ./funccount c:malloc # count all malloc() calls in libc
[all …]
|
| D | reset-trace_example.txt | 50 # ./funccount 'bash:r*'
105 I've traced 317 functions using funccount, and when I hit Ctrl-C, funccount is
113 10:00:34 PM 0 27980 87.25 10.78 0.00 98.04 3 funccount.py
118 10:00:35 PM 0 27980 77.00 23.00 0.00 100.00 3 funccount.py
122 funccount looks a lot like it's in an infinite loop (I can use a stack-sampling
|
| D | tcptop_example.txt | 42 than the packet rate. You can measure the rate of these using funccount.
|
| D | cachestat.py | 7 # Taken from funccount by Brendan Gregg
|
| /external/bcc/man/man8/ |
| D | funccount.8 | 1 .TH funccount 8 "2015-08-18" "USER COMMANDS"
3 funccount \- Count function, tracepoint, and USDT probe calls matching a pattern. Uses Linux eBPF/b…
5 .B funccount [\-h] [\-p PID] [\-i INTERVAL] [\-d DURATION] [\-T] [\-r] [\-D] pattern
45 .B funccount 'vfs_*'
49 .B funccount 'tcp_send*'
53 .B funccount \-i 1 'vfs_*'
57 .B funccount \-d 10 'vfs_*'
61 .B funccount \-r '^vfs_.*'
65 .B funccount \-p 181 'vfs_*'
69 .B funccount t:sched:sched_fork
[all …]
|
| D | funcslower.8 | 108 called (and estimate the overhead), use the funccount tool, e.g.:
110 # funccount c:open
125 funccount(8), funclatency(8), argdist(8), trace(8)
|
| D | fileslower.8 | 88 instrumented events using the bcc funccount tool, eg:
90 # ./funccount.py -i 1 -r '^__vfs_(read|write)$'
114 biosnoop(8), funccount(8)
|
| D | funclatency.8 | 118 environment and understand overheads before use. You can also use funccount
135 funccount(8)
|
| D | stackcount.8 | 127 also use funccount to get a handle on function call rates first.
142 stacksnoop(8), funccount(8)
|
| D | killsnoop.8 | 83 opensnoop(8), funccount(8)
|
| D | tcpaccept.8 | 86 tcpconnect(8), funccount(8), tcpdump(8)
|
| D | tcpconnect.8 | 111 tcpaccept(8), funccount(8), tcpdump(8)
|
| D | tcpconnlat.8 | 109 tcpconnect(8), tcpaccept(8), funccount(8), tcpdump(8)
|
| D | tcptop.8 | 90 use funccount to count the kprobes in the tool to find out this rate, as the
|
| D | opensnoop.8 | 144 funccount(1)
|
| D | syscount.8 | 110 funccount(8), ucalls(8), argdist(8), trace(8), funclatency(8)
|
| D | ext4slower.8 | 113 biosnoop(8), funccount(8), fileslower(8)
|
| D | xfsslower.8 | 113 biosnoop(8), funccount(8), fileslower(8)
|
| D | zfsslower.8 | 116 biosnoop(8), funccount(8), fileslower(8)
|
| D | nfsslower.8 | 122 biosnoop(8), funccount(8), fileslower(8)
|
| D | btrfsslower.8 | 115 btrfsdist(8), biosnoop(8), funccount(8), fileslower(8)
|
| /external/apache-xml/src/main/java/org/apache/xpath/functions/ |
| D | FuncCount.java | 19 * $Id: FuncCount.java 468655 2006-10-28 07:12:06Z minchau $
32 public class FuncCount extends FunctionOneArg class
|
| /external/bcc/snapcraft/ |
| D | snapcraft.yaml | 118 funccount:
119 command: usr/share/bcc/tools/funccount
|
| /external/bcc/examples/tracing/ |
| D | stacksnoop_example.txt | 23 funccount.
|
12