diff options
author | Jesper Dangaard Brouer <brouer@redhat.com> | 2018-01-19 17:15:50 +0100 |
---|---|---|
committer | Daniel Borkmann <daniel@iogearbox.net> | 2018-01-20 02:10:55 +0100 |
commit | 417f1d9f217922d822b64e8323458d7d03a12d4f (patch) | |
tree | 73baaad473d32b2cb33f264a6e3f064126a5d495 /samples/connector | |
parent | 05526361af7d6748edc544dc912b494473a964ef (diff) | |
download | linux-417f1d9f217922d822b64e8323458d7d03a12d4f.tar.gz linux-417f1d9f217922d822b64e8323458d7d03a12d4f.tar.bz2 linux-417f1d9f217922d822b64e8323458d7d03a12d4f.zip |
samples/bpf: xdp_monitor include cpumap tracepoints in monitoring
The xdp_redirect_cpu sample have some "builtin" monitoring of the
tracepoints for xdp_cpumap_*, but it is practical to have an external
tool that can monitor these transpoint as an easy way to troubleshoot
an application using XDP + cpumap.
Specifically I need such external tool when working on Suricata and
XDP cpumap redirect. Extend the xdp_monitor tool sample with
monitoring of these xdp_cpumap_* tracepoints. Model the output format
like xdp_redirect_cpu.
Given I needed to handle per CPU decoding for cpumap, this patch also
add per CPU info on the existing monitor events. This resembles part
of the builtin monitoring output from sample xdp_rxq_info. Thus, also
covering part of that sample in an external monitoring tool.
Performance wise, the cpumap tracepoints uses bulking, which cause
them to have very little overhead. Thus, they are enabled by default.
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'samples/connector')
0 files changed, 0 insertions, 0 deletions