diff options
| author |   David S. Miller <davem@davemloft.net> | 2017-08-29 10:51:29 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-08-29 10:51:29 -0700 |
| commit | 25d4dae1a64f7abc5d40faef08f7c7de2a5ece79 (patch) | |
| tree | fb91db813a3b9c08d734ccffe5b19465b7274902 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Merge tag 'rxrpc-next-20170829' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs (diff) | |
| parent | samples/bpf: xdp_monitor tool based on tracepoints (diff) | |
| download | wireguard-linux-25d4dae1a64f7abc5d40faef08f7c7de2a5ece79.tar.xz wireguard-linux-25d4dae1a64f7abc5d40faef08f7c7de2a5ece79.zip | |
Merge branch 'XDP-redirect-tracepoints'
Jesper Dangaard Brouer says:
====================
XDP redirect tracepoints
I feel this is as far as I can take the tracepoint infrastructure to
assist XDP monitoring.
Tracepoints comes with a base overhead of 25 nanosec for an attached
bpf_prog, and 48 nanosec for using a full perf record. This is
problematic for the XDP use-case, but it is very convenient to use the
existing perf infrastructure.
From a performance perspective, the real solution would be to attach
another bpf_prog (that understand xdp_buff), but I'm not sure we want
to introduce yet another bpf attach API for this.
One thing left is to standardize the possible err return codes, to a
limited set, to allow easier (and faster) mapping into a bpf map.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions