funclatency: user functions support #733
Conversation
When histogram keys are complex structures (`ct.Structure` created from C struct), they can't be used as dictionary keys for counting purposes without a custom hashing function. Allow the user to provide such hashing function when calling `print_log_hist` to print the histogram.
Similarly to `attach_uprobe`, `attach_uretprobe` now supports taking a regular expression.
funclatency now supports user functions (including regular expressions) in addition to kernel functions. When multiple processes are traced, the output is always per-function, per- process. When a single process is traced, the output can be combined for all traced functions (as with kernel functions). Usage examples: ``` funclatency pthread:*mutex* -p 6449 -F funclatency c:read funclatency dd:* -p $(pidof dd) -uF ```
86640c7
to
80d61f1
Compare
|
LGTM cc @brendangregg |
|
LGTM, and tested, works, and is pretty amazing. Thanks @goldshtn ! @4ast please merge (I don't have that button) @goldshtn funccount next? :) I actually use funccount more than funclatency -- funccount is good for checking the rate of function calls before doing anything more expensive. Plus, my old perf-tools funccount is kernel only (ftrace); this will be the first funccount that can do both. |
|
... we'll eventually need to update the reference-guide for the other bits that have been added... |
|
@brendangregg Thanks :) Yes, |
This introduces user functions support in
funclatency. It's quite useful as a mini-profiler or just another way to quickly probe the latency of a particular function in user space.Usage examples: