@@ -7,21 +7,20 @@ hooks on xdp:exception tracepoint and get its values to user space
77stats application.
88
99* Table of Contents :TOC:
10- - [[#using-libbpf][XDP tracepoints]]
11- - [[#xdp-tracepoints][XDP tracepoints]]
10+ - [[#xdp-tracepoints][XDP tracepoints]]
1211 - [[#tracepoint-program-section][Tracepoint program section]]
1312 - [[#tracepoint-arguments][Tracepoint arguments]]
1413 - [[#tracepoint-attaching][Tracepoint attaching]]
1514 - [[#hash-map][HASH map]]
1615- [[#assignments][Assignments]]
17- - [[#assignment-1][Assignment 1: Setting up your test lab]]
18- - [[#assignment-2][Assignment 2: Load tracepoint monitor program]]
16+ - [[#assignment-1-setting-up-your-test-lab ][Assignment 1: Setting up your test lab]]
17+ - [[#assignment-2-load-tracepoint-monitor-program ][Assignment 2: Load tracepoint monitor program]]
1918
2019
2120* XDP tracepoints
2221
2322The eBPF programs can be attached also to tracepoints. There are
24- several tracepoints related to xdp:
23+ several tracepoints related to the xdp tracepoint subsystem :
2524
2625#+begin_example sh
2726ls /sys/kernel/debug/tracing/events/xdp/
@@ -41,13 +40,11 @@ The bpf library expects the tracepoint eBPF program to be stored
4140in a section with following name:
4241
4342#+begin_example sh
44- tracepoint/sys/ tracepoint
43+ tracepoint/< sys>/< tracepoint>
4544#+end_example
4645
47- where 'sys' is the tracepoint subsystem and 'tracepoint' is
48- the tracepoint name.
49-
50- which can be done with following construct:
46+ where =<sys>= is the tracepoint subsystem and =<tracepoint>= is
47+ the tracepoint name, which can be done with following construct:
5148
5249#+begin_example sh
5350SEC("tracepoint/xdp/xdp_exception")
0 commit comments