diff options
author | Jesper Dangaard Brouer <brouer@redhat.com> | 2018-01-03 11:25:13 +0100 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2018-01-05 15:21:20 -0800 |
commit | aecd67b60722dd24353b0bc50e78a55b30707dcd (patch) | |
tree | d9c107a5ab64864470ab7d2173340cc428cd562c /include/target | |
parent | 5f103c5d4dbadec0f2cacd39b6429e1b8a8cf983 (diff) | |
download | talos-obmc-linux-aecd67b60722dd24353b0bc50e78a55b30707dcd.tar.gz talos-obmc-linux-aecd67b60722dd24353b0bc50e78a55b30707dcd.zip |
xdp: base API for new XDP rx-queue info concept
This patch only introduce the core data structures and API functions.
All XDP enabled drivers must use the API before this info can used.
There is a need for XDP to know more about the RX-queue a given XDP
frames have arrived on. For both the XDP bpf-prog and kernel side.
Instead of extending xdp_buff each time new info is needed, the patch
creates a separate read-mostly struct xdp_rxq_info, that contains this
info. We stress this data/cache-line is for read-only info. This is
NOT for dynamic per packet info, use the data_meta for such use-cases.
The performance advantage is this info can be setup at RX-ring init
time, instead of updating N-members in xdp_buff. A possible (driver
level) micro optimization is that xdp_buff->rxq assignment could be
done once per XDP/NAPI loop. The extra pointer deref only happens for
program needing access to this info (thus, no slowdown to existing
use-cases).
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'include/target')
0 files changed, 0 insertions, 0 deletions