summaryrefslogtreecommitdiff
path: root/Documentation/networking
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-04-10 09:51:09 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-04-10 09:51:09 +0300
commit039535ecf18e8dc93fe4b294fdf175a31bd023b2 (patch)
tree4a70d5db5ba3f1c0fdb1e7dc29f16fa7ace044c4 /Documentation/networking
parentb2ea273a477cd6e83daedbfa1981cd1a7468f73a (diff)
parent09a9639e56c01c7a00d6c0ca63f4c7c41abe075d (diff)
downloadlinux-039535ecf18e8dc93fe4b294fdf175a31bd023b2.tar.xz
Merge 6.3-rc6 into tty-next
We need the tty/serial fixes in here for testing. Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/networking')
-rw-r--r--Documentation/networking/xdp-rx-metadata.rst7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/networking/xdp-rx-metadata.rst b/Documentation/networking/xdp-rx-metadata.rst
index aac63fc2d08b..25ce72af81c2 100644
--- a/Documentation/networking/xdp-rx-metadata.rst
+++ b/Documentation/networking/xdp-rx-metadata.rst
@@ -23,10 +23,13 @@ metadata is supported, this set will grow:
An XDP program can use these kfuncs to read the metadata into stack
variables for its own consumption. Or, to pass the metadata on to other
consumers, an XDP program can store it into the metadata area carried
-ahead of the packet.
+ahead of the packet. Not all packets will necessary have the requested
+metadata available in which case the driver returns ``-ENODATA``.
Not all kfuncs have to be implemented by the device driver; when not
-implemented, the default ones that return ``-EOPNOTSUPP`` will be used.
+implemented, the default ones that return ``-EOPNOTSUPP`` will be used
+to indicate the device driver have not implemented this kfunc.
+
Within an XDP frame, the metadata layout (accessed via ``xdp_buff``) is
as follows::