On Tue, Dec 13, 2022 at 8:37 AM David Vernet <void@xxxxxxxxxxxxx> wrote: > > On Mon, Dec 12, 2022 at 06:35:51PM -0800, Stanislav Fomichev wrote: > > Document all current use-cases and assumptions. > > > > Cc: John Fastabend <john.fastabend@xxxxxxxxx> > > Cc: David Ahern <dsahern@xxxxxxxxx> > > Cc: Martin KaFai Lau <martin.lau@xxxxxxxxx> > > Cc: Jakub Kicinski <kuba@xxxxxxxxxx> > > Cc: Willem de Bruijn <willemb@xxxxxxxxxx> > > Cc: Jesper Dangaard Brouer <brouer@xxxxxxxxxx> > > Cc: Anatoly Burakov <anatoly.burakov@xxxxxxxxx> > > Cc: Alexander Lobakin <alexandr.lobakin@xxxxxxxxx> > > Cc: Magnus Karlsson <magnus.karlsson@xxxxxxxxx> > > Cc: Maryam Tahhan <mtahhan@xxxxxxxxxx> > > Cc: xdp-hints@xxxxxxxxxxxxxxx > > Cc: netdev@xxxxxxxxxxxxxxx > > Signed-off-by: Stanislav Fomichev <sdf@xxxxxxxxxx> > > --- > > Documentation/bpf/xdp-rx-metadata.rst | 90 +++++++++++++++++++++++++++ > > 1 file changed, 90 insertions(+) > > create mode 100644 Documentation/bpf/xdp-rx-metadata.rst > > > > diff --git a/Documentation/bpf/xdp-rx-metadata.rst b/Documentation/bpf/xdp-rx-metadata.rst > > new file mode 100644 > > index 000000000000..498eae718275 > > --- /dev/null > > +++ b/Documentation/bpf/xdp-rx-metadata.rst > > I think you need to add this to Documentation/bpf/index.rst. Or even > better, maybe it's time to add an xdp/ subdirectory and put all docs > there? Don't want to block your patchset from bikeshedding on this > point, so for now it's fine to just put it in > Documentation/bpf/index.rst until we figure that out. Maybe let's put it under Documentation/networking/xdp-rx-metadata.rst and reference form Documentation/networking/index.rst? Since it's more relevant to networking than the core bpf? > > @@ -0,0 +1,90 @@ > > +=============== > > +XDP RX Metadata > > +=============== > > + > > +XDP programs support creating and passing custom metadata via > > +``bpf_xdp_adjust_meta``. This metadata can be consumed by the following > > +entities: > > Can you add a couple of sentences to this intro section that explains > what metadata is at a high level? I'm gonna copy-paste here what I'm adding, feel free to reply back if still unclear. (so we don't have to wait another week to discuss the changes) XDP programs support creating and passing custom metadata via ``bpf_xdp_adjust_meta``. The metadata can contain some extra information about the packet: timestamps, hash, vlan and tunneling information, etc. This metadata can be consumed by the following entities: > > + > > +1. ``AF_XDP`` consumer. > > +2. Kernel core stack via ``XDP_PASS``. > > +3. Another device via ``bpf_redirect_map``. > > +4. Other BPF programs via ``bpf_tail_call``. > > + > > +General Design > > +============== > > + > > +XDP has access to a set of kfuncs to manipulate the metadata. Every > > "...to manipulate the metadata in an XDP frame." ? SG! > > +device driver implements these kfuncs. The set of kfuncs is > > "Every device driver implements these kfuncs" can you be a bit more > specific about which types of device drivers will implement these? How about the following? Every device driver that wishes to expose additional packet metadata can implement these kfuncs. > > +declared in ``include/net/xdp.h`` via ``XDP_METADATA_KFUNC_xxx``. > > Why is it suffixed with _xxx? I'm following the precedent of BTF_SOCK_TYPE_xxx and BTF_TRACING_TYPE_xxx. LMK if you prefer a better name here. > > + > > +Currently, the following kfuncs are supported. In the future, as more > > +metadata is supported, this set will grow: > > + > > +- ``bpf_xdp_metadata_rx_timestamp_supported`` returns true/false to > > + indicate whether the device supports RX timestamps > > +- ``bpf_xdp_metadata_rx_timestamp`` returns packet RX timestamp > > s/returns packet/returns a packet's ty! > > +- ``bpf_xdp_metadata_rx_hash_supported`` returns true/false to > > + indicate whether the device supports RX hash > > I don't see bpf_xdp_metadata_rx_timestamp_supported() or > bpf_xdp_metadata_rx_hash_supported() being added in your patch set. Can > you remove these entries until they're actually implemented? Ooh, good catch, I've removed them for this round. Will remove from the doc as well. > > +- ``bpf_xdp_metadata_rx_hash`` returns packet RX hash > > We should probably also add a note that these kfuncs currently just > return -EOPNOTSUPP. The default ones return EOPNOTSUPP. Maybe I can clarify with the following? Not all kfuncs have to be implemented by the device driver; when not implemented, the default ones that return ``-EOPNOTSUPP`` will be used. > Finally, should we add either some example code showing how to use these > kfuncs, or at the very least some links to their selftests so readers > have example code they can refer to? Good idea, will reference tools/testing/selftests/bpf/progs/xdp_metadata.c and tools/testing/selftests/bpf/prog_tests/xdp_metadata.c. Example ======= See ``tools/testing/selftests/bpf/progs/xdp_metadata.c`` and ``tools/testing/selftests/bpf/prog_tests/xdp_metadata.c`` for an example of BPF program that handles XDP metadata. > > + > > +Within the XDP frame, the metadata layout is as follows:: > > + > > + +----------+-----------------+------+ > > + | headroom | custom metadata | data | > > + +----------+-----------------+------+ > > + ^ ^ > > + | | > > + xdp_buff->data_meta xdp_buff->data > > + > > +AF_XDP > > +====== > > + > > +``AF_XDP`` use-case implies that there is a contract between the BPF program > > +that redirects XDP frames into the ``XSK`` and the final consumer. > > Can you fully spell out what XSK stands for the first time it's used? > Something like "...that redirects XDP frames into the ``AF_XDP`` socket > (``XSK``) and the final consumer." Applies anywhere else you think > appropriate as well. SG! > > +Thus the BPF program manually allocates a fixed number of > > +bytes out of metadata via ``bpf_xdp_adjust_meta`` and calls a subset > > +of kfuncs to populate it. User-space ``XSK`` consumer, looks > > s/User-space/The user-space > > Also, it feels like it might read better without the comma, and by > doing something like s/looks at/computes. Wdyt? Ageed. > > +at ``xsk_umem__get_data() - METADATA_SIZE`` to locate its metadata. > > + > > +Here is the ``AF_XDP`` consumer layout (note missing ``data_meta`` pointer):: > > + > > + +----------+-----------------+------+ > > + | headroom | custom metadata | data | > > + +----------+-----------------+------+ > > + ^ > > + | > > + rx_desc->address > > + > > +XDP_PASS > > +======== > > + > > +This is the path where the packets processed by the XDP program are passed > > +into the kernel. The kernel creates ``skb`` out of the ``xdp_buff`` contents. > > s/creates ``skb``/creates the ``skb`` Ack. > > +Currently, every driver has a custom kernel code to parse the descriptors and > > +populate ``skb`` metadata when doing this ``xdp_buff->skb`` conversion. > > +In the future, we'd like to support a case where XDP program can override > > s/where XDP program/where an XDP program Same here, will fix, thanks! > > +some of that metadata. > > + > > +The plan of record is to make this path similar to ``bpf_redirect_map`` > > +so the program can control which metadata is passed to the skb layer. > > + > > +bpf_redirect_map > > +================ > > + > > +``bpf_redirect_map`` can redirect the frame to a different device. > > +In this case we don't know ahead of time whether that final consumer > > +will further redirect to an ``XSK`` or pass it to the kernel via ``XDP_PASS``. > > +Additionally, the final consumer doesn't have access to the original > > +hardware descriptor and can't access any of the original metadata. > > + > > +For this use-case, only custom metadata is currently supported. If > > +the frame is eventually passed to the kernel, the skb created from such > > +a frame won't have any skb metadata. The ``XSK`` consumer will only > > +have access to the custom metadata. > > + > > +bpf_tail_call > > +============= > > + > > +No special handling here. Tail-called program operates on the same context > > s/Tail-called program/A tail-called program Ty! > > +as the original one. > > -- > > 2.39.0.rc1.256.g54fd8350bd-goog > >
