Lines Matching refs:that

13 table" that userspace populates with "flows" that map from keys based
34 protocols that have become obsolete.  Therefore, the Netlink interface
40 flow key that it parsed from the packet.  Userspace then extracts its
59       that the kernel considers part of the flow must go to userspace,
61       determine that the values of the extra fields would not affect
73 information about a packet that cannot be extracted from the packet
83 corresponding to a TCP packet that arrived on vport 1:
111 that the kernel does not implement will simply result in additional flow setups.
112 The kernel module will also work with user space programs that neither support
128 responsibility of the user space program to ensure that any incoming packet
141 User space programs that support UFID are expected to provide it during flow
151 compatibility for applications that follow the rules listed under
163 through a few examples.  Suppose, for example, that the kernel module
179 But this change would negatively affect a userspace application that
182 ignore the "vlan" attribute that it does not understand and therefore
183 assume that the flow contained IP packets.  This is a bad assumption
196 nested inside the "encap" attribute.  Thus, an application that does
206 simple Ethernet switch that forwards every packet.
214 For example, consider a packet that contains an IP header that
216 header, so that the TCP header is missing.  The flow key for this
223 indicating that a VLAN TCI should follow, but which is truncated just
230 all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka
247       compare entire flow keys that it may not be able to fully