On 11/12/15 4:09 PM, Kornievskaia, Olga wrote:
Just to elaborate further, what I’m interested in timings of NFS operations, so
I’m not using any new tracepoints, but just the ones that are present in the
code. However since NFS doesn’t various things outside of the process calling
into NFS then will “perf trace” still work?
I’m using “perf record -e ‘nfs4:*’,’nfs:*’ -ag” command to generate tracing
info. That captures tracepoints executed by the application as well as the
kernel threads that do asynchronous IO.
Do you really need callchains? (-g option)
After the perf-record run perf-script to dump the samples. Pipe that
into an awk script (or python or bash or ...) and you can compute what
you want.
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
