Home
last modified time | relevance | path

Searched full:funccount (Results 1 – 25 of 38) sorted by relevance

12

/external/bcc/tools/
Dfunccount_example.txt1 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 …]
Dfunccount.py4 # funccount Count functions, tracepoints, and USDT probes.
7 # USAGE: funccount [-h] [-p PID] [-i INTERVAL] [-d DURATION] [-T] [-r]
221 ./funccount 'vfs_*' # count kernel fns starting with "vfs"
222 ./funccount -r '^vfs.*' # same as above, using regular expressions
223 ./funccount -Ti 5 'vfs_*' # output every 5 seconds, with timestamps
224 ./funccount -d 10 'vfs_*' # trace for 10 seconds only
225 ./funccount -p 185 'vfs_*' # count vfs calls for PID 181 only
226 ./funccount t:sched:sched_fork # count calls to the sched_fork tracepoint
227 ./funccount -p 185 u:node:gc* # count all GC USDT probes in node, PID 185
228 ./funccount c:malloc # count all malloc() calls in libc
[all …]
Dreset-trace_example.txt50 # ./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
/external/bcc/man/man8/
Dfunccount.81 .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
48 .B funccount 'vfs_*'
52 .B funccount 'tcp_send*'
56 .B funccount \-i 1 'vfs_*'
60 .B funccount \-d 10 'vfs_*'
64 .B funccount \-r '^vfs_.*'
68 .B funccount \-p 181 'vfs_*'
72 .B funccount t:sched:sched_fork
[all …]
Dfuncslower.8108 called (and estimate the overhead), use the funccount tool, e.g.:
110 # funccount c:open
125 funccount(8), funclatency(8), argdist(8), trace(8)
Dfileslower.888 instrumented events using the bcc funccount tool, eg:
90 # ./funccount.py -i 1 -r '^__vfs_(read|write)$'
114 biosnoop(8), funccount(8)
Dfuncinterval.8105 environment and understand overheads before use. You can also use funccount
123 funccount(8)
Dfunclatency.8121 environment and understand overheads before use. You can also use funccount
138 funccount(8)
Dstackcount.8143 also use funccount to get a handle on function call rates first.
158 stacksnoop(8), funccount(8)
Dvirtiostat.866 iostat(1), iftop(8), funccount(8)
Dkillsnoop.890 opensnoop(8), funccount(8)
Dtcprtt.8103 tcptracer(8), tcpconnect(8), funccount(8), tcpdump(8)
Dtcpaccept.8126 tcptracer(8), tcpconnect(8), funccount(8), tcpdump(8)
Dsyscount.8110 funccount(8), ucalls(8), argdist(8), trace(8), funclatency(8)
Dxfsslower.8113 biosnoop(8), funccount(8), fileslower(8)
Dtcpconnlat.8133 tcpconnect(8), tcpaccept(8), funccount(8), tcpdump(8)
Dopensnoop.8156 execsnoop(8), funccount(1)
Dext4slower.8113 biosnoop(8), funccount(8), fileslower(8)
Dbtrfsslower.8122 btrfsdist(8), biosnoop(8), funccount(8), fileslower(8)
Dtcptop.8115 use funccount to count the kprobes in the tool to find out this rate, as the
Dnfsslower.8122 biosnoop(8), funccount(8), fileslower(8)
Dzfsslower.8116 biosnoop(8), funccount(8), fileslower(8)
/external/apache-xml/src/main/java/org/apache/xpath/functions/
DFuncCount.java19 * $Id: FuncCount.java 468655 2006-10-28 07:12:06Z minchau $
32 public class FuncCount extends FunctionOneArg class
/external/bcc/snap/
Dsnapcraft.yaml168 funccount:
169 command: bcc-wrapper funccount
/external/bcc/examples/tracing/
Dstacksnoop_example.txt23 funccount.

12