Lines Matching refs:it

12 within a bridge).  Each datapath also has associated with it a "flow
18 When a packet arrives on a vport, the kernel module processes it by
19 extracting its flow key and looking it up in the flow table.  If there
20 is a matching flow, it executes the associated actions.  If there is
21 no match, it queues the packet to userspace for processing (as part of
31 kernel module to remain relevant, it must be possible for newer
39 kernel module passes a packet to userspace, it also passes along the
40 flow key that it parsed from the packet.  Userspace then extracts its
41 own notion of a flow key from the packet and compares it against the
49       headers but userspace stopped at the Ethernet type (because it
52       as long as it uses the kernel-provided flow key to do it.
62       forwarding behavior, then it could set up a flow anyway.)
115 Since the kernel may ignore or modify wildcard bits, it can be difficult for
141 User space programs that support UFID are expected to provide it during flow
162 This rule does have less-obvious consequences so it is worth working
164 did not already implement VLAN parsing.  Instead, it just interpreted
171 Naively, to add VLAN support, it makes sense to add a new "vlan" flow
182 ignore the "vlan" attribute that it does not understand and therefore
185 802.1Q header) and it could cause the application's behavior to change
186 across kernel versions even though it follows the compatibility rules.
245     - When the kernel sends a given flow key to userspace, it always
246       composes it the same way.  This allows userspace to hash and
247       compare entire flow keys that it may not be able to fully