Lines Matching refs:packet

5 flow-level packet processing on selected network devices.  It can be
14 on packet headers and metadata to sets of actions.  The most common
15 action forwards the packet to another vport; other actions are also
18 When a packet arrives on a vport, the kernel module processes it by
21 no match, it queues the packet to userspace for processing (as part of
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
44     - If userspace's notion of the flow key for the packet matches the
57       forward the packet manually, without setting up a flow in the
58       kernel.  This case is bad for performance because every packet
72 attributes.  Some attributes represent packet metadata, defined as any
73 information about a packet that cannot be extracted from the packet
74 itself, e.g. the vport on which the packet was received.  Most
75 attributes, however, are extracted from headers within the packet,
83 corresponding to a TCP packet that arrived on vport 1:
104 of a incoming packet. Using wildcarded flow can improve the flow set up rate
128 responsibility of the user space program to ensure that any incoming packet
166 packet.  The flow key for any packet with an 802.1Q header would look
174 definitions.  With this change, a TCP packet in VLAN 10 would have a
189 example, why 802.1Q support uses nested attributes.  A TCP packet in
206 simple Ethernet switch that forwards every packet.
214 For example, consider a packet that contains an IP header that
217 packet would include a tcp attribute with all-zero src and dst, like
222 As another example, consider a packet with an Ethernet type of 0x8100,
224 after the Ethernet type.  The flow key for this packet would include
229 Unlike a TCP packet with source and destination ports 0, an