summaryrefslogtreecommitdiff
path: root/samples/bpf/tracex1_kern.c
diff options
context:
space:
mode:
authorJesper Dangaard Brouer <brouer@redhat.com>2018-01-19 19:15:50 +0300
committerDaniel Borkmann <daniel@iogearbox.net>2018-01-20 04:10:55 +0300
commit417f1d9f217922d822b64e8323458d7d03a12d4f (patch)
tree73baaad473d32b2cb33f264a6e3f064126a5d495 /samples/bpf/tracex1_kern.c
parent05526361af7d6748edc544dc912b494473a964ef (diff)
downloadlinux-417f1d9f217922d822b64e8323458d7d03a12d4f.tar.xz
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/bpf/tracex1_kern.c')
0 files changed, 0 insertions, 0 deletions