Lines Matching refs:key

22 extracting its flow key and looking it up in the flow table.  If there
29 Flow key compatibility
35 versions to parse additional protocols as part of the flow key.  It
39 applications to work with any version of the flow key, past or future.
43 flow key that it parsed from the packet.  Userspace then extracts its
44 own notion of a flow key from the packet and compares it against the
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
51       version of the flow key, for example if the kernel decoded IPv6
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
71 Flow key format
74 A flow key is passed over a Netlink socket as a sequence of Netlink
83 flow key attributes.  For informal explanatory purposes here, we write
85 and nesting.  For example, the following could represent a flow key
97 Wildcarded flow key format
101 passed over the Netlink socket. A flow key, exactly as described above, and an
105 in the mask specifies a exact match with the corresponding bit in the flow key.
125 of the key exactly as originally installed. This will provides a handle to
140 An alternative to using the original match portion of a key as the handle for
147 flow key if a UFID is specified.
155 "Flow key compatibility" above.
161     key attributes.  It must not change the meaning of already defined
162     flow key attributes.
169 packet.  The flow key for any packet with an 802.1Q header would look
175 key attribute to contain the VLAN tag, then continue to decode the
178 flow key much like this::
183 has not been updated to understand the new "vlan" flow key attribute.
198 Notice how the "eth_type", "ip", and "tcp" flow key attributes are
200 not understand the "vlan" key will not see either of those attributes
219 header, so that the TCP header is missing.  The flow key for this
227 after the Ethernet type.  The flow key for this packet would include
236 Thus, the flow key in this second example unambiguously indicates a
248     - When the kernel sends a given flow key to userspace, it always