diff options
author | Toke Høiland-Jørgensen <toke@redhat.com> | 2019-12-16 12:07:42 +0100 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2019-12-16 07:05:38 -0800 |
commit | d50ecc46d18fa19ccf06e0c4d2ee8a050c665e3d (patch) | |
tree | b60ffa2c725d450b8f336af5283ddc733ba8da21 /tools/lib | |
parent | 450278977acbf494a20367c22fbb38729772d1fc (diff) | |
download | linux-d50ecc46d18fa19ccf06e0c4d2ee8a050c665e3d.tar.gz linux-d50ecc46d18fa19ccf06e0c4d2ee8a050c665e3d.tar.bz2 linux-d50ecc46d18fa19ccf06e0c4d2ee8a050c665e3d.zip |
samples/bpf: Attach XDP programs in driver mode by default
When attaching XDP programs, userspace can set flags to request the attach
mode (generic/SKB mode, driver mode or hw offloaded mode). If no such flags
are requested, the kernel will attempt to attach in driver mode, and then
silently fall back to SKB mode if this fails.
The silent fallback is a major source of user confusion, as users will try
to load a program on a device without XDP support, and instead of an error
they will get the silent fallback behaviour, not notice, and then wonder
why performance is not what they were expecting.
In an attempt to combat this, let's switch all the samples to default to
explicitly requesting driver-mode attach. As part of this, ensure that all
the userspace utilities have a switch to enable SKB mode. For those that
have a switch to request driver mode, keep it but turn it into a no-op.
Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
Acked-by: David Ahern <dsahern@gmail.com>
Link: https://lore.kernel.org/bpf/20191216110742.364456-1-toke@redhat.com
Diffstat (limited to 'tools/lib')
0 files changed, 0 insertions, 0 deletions