Lines Matching +full:nested +full:- +full:attributes

1 .. SPDX-License-Identifier: GPL-2.0
8 flow-level packet processing on selected network devices.  It can be
10 VLAN processing, network access control, flow-based network control,
26 packets of the same type entirely in-kernel).
30 ----------------------
45 kernel-provided version:
47     - If userspace's notion of the flow key for the packet matches the
50     - If the kernel's flow key includes more fields than the userspace
55       as long as it uses the kernel-provided flow key to do it.
57     - If the userspace flow key includes more fields than the
72 ---------------
75 attributes.  Some attributes represent packet metadata, defined as any
78 attributes, however, are extracted from headers within the packet,
83 flow key attributes.  For informal explanatory purposes here, we write
84 them as comma-separated strings, with parentheses indicating arguments
98 --------------------------
100 A wildcarded flow is described with two sequences of Netlink attributes
116 nor supply flow mask attributes.
133 performs best-effort detection of overlapping wildcarded flows and may reject
138 -----------------------
151 ---------------------------------
161     key attributes.  It must not change the meaning of already defined
162     flow key attributes.
165 This rule does have less-obvious consequences so it is worth working
191 The solution is to use a set of nested attributes.  This is, for
192 example, why 802.1Q support uses nested attributes.  A TCP packet in
198 Notice how the "eth_type", "ip", and "tcp" flow key attributes are
199 nested inside the "encap" attribute.  Thus, an application that does
200 not understand the "vlan" key will not see either of those attributes
205 --------------------------
220 packet would include a tcp attribute with all-zero src and dst, like
228 an all-zero-bits vlan and an empty encap attribute, like this::
233 all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka
240 -----------
244     - Duplicate attributes are not allowed at a given nesting level.
246     - Ordering of attributes is not significant.
248     - When the kernel sends a given flow key to userspace, it always