1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2016 6WIND S.A.
3 Copyright 2016 Mellanox Technologies, Ltd
5 Generic flow API (rte_flow)
6 ===========================
11 This API provides a generic means to configure hardware to match specific
12 ingress or egress traffic, alter its fate and query related counters
13 according to any number of user-defined rules.
15 It is named *rte_flow* after the prefix used for all its symbols, and is
16 defined in ``rte_flow.h``.
18 - Matching can be performed on packet data (protocol headers, payload) and
19 properties (e.g. associated physical port, virtual device function ID).
21 - Possible operations include dropping traffic, diverting it to specific
22 queues, to virtual/physical device functions or ports, performing tunnel
23 offloads, adding marks and so on.
31 A flow rule is the combination of attributes with a matching pattern and a
32 list of actions. Flow rules form the basis of this API.
34 Flow rules can have several distinct actions (such as counting,
35 encapsulating, decapsulating before redirecting packets to a particular
36 queue, etc.), instead of relying on several rules to achieve this and having
37 applications deal with hardware implementation details regarding their
40 Support for different priority levels on a rule basis is provided, for
41 example in order to force a more specific rule to come before a more generic
42 one for packets matched by both. However hardware support for more than a
43 single priority level cannot be guaranteed. When supported, the number of
44 available priority levels is usually low, which is why they can also be
45 implemented in software by PMDs (e.g. missing priority levels may be
46 emulated by reordering rules).
48 In order to remain as hardware-agnostic as possible, by default all rules
49 are considered to have the same priority, which means that the order between
50 overlapping rules (when a packet is matched by several filters) is
53 PMDs may refuse to create overlapping rules at a given priority level when
54 they can be detected (e.g. if a pattern matches an existing filter).
56 Thus predictable results for a given priority level can only be achieved
57 with non-overlapping rules, using perfect matching on all protocol layers.
59 Flow rules can also be grouped, the flow rule priority is specific to the
60 group they belong to. All flow rules in a given group are thus processed within
61 the context of that group. Groups are not linked by default, so the logical
62 hierarchy of groups must be explicitly defined by flow rules themselves in each
63 group using the JUMP action to define the next group to redirect too. Only flow
64 rules defined in the default group 0 are guarantee to be matched against, this
65 makes group 0 the origin of any group hierarchy defined by an application.
67 Support for multiple actions per rule may be implemented internally on top
68 of non-default hardware priorities, as a result both features may not be
69 simultaneously available to applications.
71 Considering that allowed pattern/actions combinations cannot be known in
72 advance and would result in an impractically large number of capabilities to
73 expose, a method is provided to validate a given rule from the current
74 device configuration state.
76 This enables applications to check if the rule types they need is supported
77 at initialization time, before starting their data path. This method can be
78 used anytime, its only requirement being that the resources needed by a rule
79 should exist (e.g. a target RX queue should be configured first).
81 Each defined rule is associated with an opaque handle managed by the PMD,
82 applications are responsible for keeping it. These can be used for queries
83 and rules management, such as retrieving counters or other data and
86 To avoid resource leaks on the PMD side, handles must be explicitly
87 destroyed by the application before releasing associated resources such as
90 The following sections cover:
92 - **Attributes** (represented by ``struct rte_flow_attr``): properties of a
93 flow rule such as its direction (ingress or egress) and priority.
95 - **Pattern item** (represented by ``struct rte_flow_item``): part of a
96 matching pattern that either matches specific packet data or traffic
97 properties. It can also describe properties of the pattern itself, such as
100 - **Matching pattern**: traffic properties to look for, a combination of any
103 - **Actions** (represented by ``struct rte_flow_action``): operations to
104 perform whenever a packet is matched by a pattern.
112 Flow rules can be grouped by assigning them a common group number. Groups
113 allow a logical hierarchy of flow rule groups (tables) to be defined. These
114 groups can be supported virtually in the PMD or in the physical device.
115 Group 0 is the default group and this is the only group which flows are
116 guarantee to matched against, all subsequent groups can only be reached by
117 way of the JUMP action from a matched flow rule.
119 Although optional, applications are encouraged to group similar rules as
120 much as possible to fully take advantage of hardware capabilities
121 (e.g. optimized matching) and work around limitations (e.g. a single pattern
122 type possibly allowed in a given group), while being aware that the groups
123 hierarchies must be programmed explicitly.
125 Note that support for more than a single group is not guaranteed.
130 A priority level can be assigned to a flow rule, lower values
131 denote higher priority, with 0 as the maximum.
133 Priority levels are arbitrary and up to the application, they do
134 not need to be contiguous nor start from 0, however the maximum number
135 varies between devices and may be affected by existing flow rules.
137 A flow which matches multiple rules in the same group will always matched by
138 the rule with the highest priority in that group.
140 If a packet is matched by several rules of a given group for a given
141 priority level, the outcome is undefined. It can take any path, may be
142 duplicated or even cause unrecoverable errors.
144 Note that support for more than a single priority level is not guaranteed.
146 Attribute: Traffic direction
147 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
149 Flow rule patterns apply to inbound and/or outbound traffic.
151 In the context of this API, **ingress** and **egress** respectively stand
152 for **inbound** and **outbound** based on the standpoint of the application
153 creating a flow rule.
155 There are no exceptions to this definition.
157 Several pattern items and actions are valid and can be used in both
158 directions. At least one direction must be specified.
160 Specifying both directions at once for a given rule is not recommended but
161 may be valid in a few cases.
166 Instead of simply matching the properties of traffic as it would appear on a
167 given DPDK port ID, enabling this attribute transfers a flow rule to the
168 lowest possible level of any device endpoints found in the pattern.
170 When supported, this effectively enables an application to reroute traffic
171 not necessarily intended for it (e.g. coming from or addressed to different
172 physical ports, VFs or applications) at the device level.
174 It complements the behavior of some pattern items such as `Item: PHY_PORT`_
175 and is meaningless without them.
177 When transferring flow rules, **ingress** and **egress** attributes
178 (`Attribute: Traffic direction`_) keep their original meaning, as if
179 processing traffic emitted or received by the application.
184 Pattern items fall in two categories:
186 - Matching protocol headers and packet data, usually associated with a
187 specification structure. These must be stacked in the same order as the
188 protocol layers to match inside packets, starting from the lowest.
190 - Matching meta-data or affecting pattern processing, often without a
191 specification structure. Since they do not match packet contents, their
192 position in the list is usually not relevant.
194 Item specification structures are used to match specific values among
195 protocol fields (or item properties). Documentation describes for each item
196 whether they are associated with one and their type name if so.
198 Up to three structures of the same type can be set for a given item:
200 - ``spec``: values to match (e.g. a given IPv4 address).
202 - ``last``: upper bound for an inclusive range with corresponding fields in
205 - ``mask``: bit-mask applied to both ``spec`` and ``last`` whose purpose is
206 to distinguish the values to take into account and/or partially mask them
207 out (e.g. in order to match an IPv4 address prefix).
209 Usage restrictions and expected behavior:
211 - Setting either ``mask`` or ``last`` without ``spec`` is an error.
213 - Field values in ``last`` which are either 0 or equal to the corresponding
214 values in ``spec`` are ignored; they do not generate a range. Nonzero
215 values lower than those in ``spec`` are not supported.
217 - Setting ``spec`` and optionally ``last`` without ``mask`` causes the PMD
218 to use the default mask defined for that item (defined as
219 ``rte_flow_item_{name}_mask`` constants).
221 - Not setting any of them (assuming item type allows it) is equivalent to
222 providing an empty (zeroed) ``mask`` for broad (nonspecific) matching.
224 - ``mask`` is a simple bit-mask applied before interpreting the contents of
225 ``spec`` and ``last``, which may yield unexpected results if not used
226 carefully. For example, if for an IPv4 address field, ``spec`` provides
227 *10.1.2.3*, ``last`` provides *10.3.4.5* and ``mask`` provides
228 *255.255.0.0*, the effective range becomes *10.1.0.0* to *10.3.255.255*.
230 Example of an item specification matching an Ethernet header:
232 .. _table_rte_flow_pattern_item_example:
234 .. table:: Ethernet item
236 +----------+----------+-----------------------+
237 | Field | Subfield | Value |
238 +==========+==========+=======================+
239 | ``spec`` | ``src`` | ``00:00:01:02:03:04`` |
240 | +----------+-----------------------+
241 | | ``dst`` | ``00:00:2a:66:00:01`` |
242 | +----------+-----------------------+
243 | | ``type`` | ``0x22aa`` |
244 +----------+----------+-----------------------+
245 | ``last`` | unspecified |
246 +----------+----------+-----------------------+
247 | ``mask`` | ``src`` | ``00:00:ff:ff:ff:00`` |
248 | +----------+-----------------------+
249 | | ``dst`` | ``00:00:00:00:00:ff`` |
250 | +----------+-----------------------+
251 | | ``type`` | ``0x0000`` |
252 +----------+----------+-----------------------+
254 Non-masked bits stand for any value (shown as ``?`` below), Ethernet headers
255 with the following properties are thus matched:
257 - ``src``: ``??:??:01:02:03:??``
258 - ``dst``: ``??:??:??:??:??:01``
259 - ``type``: ``0x????``
264 A pattern is formed by stacking items starting from the lowest protocol
265 layer to match. This stacking restriction does not apply to meta items which
266 can be placed anywhere in the stack without affecting the meaning of the
269 Patterns are terminated by END items.
273 .. _table_rte_flow_tcpv4_as_l4:
275 .. table:: TCPv4 as L4
291 .. _table_rte_flow_tcpv6_in_vxlan:
293 .. table:: TCPv6 in VXLAN
295 +-------+------------+
297 +=======+============+
299 +-------+------------+
301 +-------+------------+
303 +-------+------------+
305 +-------+------------+
307 +-------+------------+
309 +-------+------------+
311 +-------+------------+
313 +-------+------------+
317 .. _table_rte_flow_tcpv4_as_l4_meta:
319 .. table:: TCPv4 as L4 with meta items
341 The above example shows how meta items do not affect packet data matching
342 items, as long as those remain stacked properly. The resulting matching
343 pattern is identical to "TCPv4 as L4".
345 .. _table_rte_flow_udpv6_anywhere:
347 .. table:: UDPv6 anywhere
359 If supported by the PMD, omitting one or several protocol layers at the
360 bottom of the stack as in the above example (missing an Ethernet
361 specification) enables looking up anywhere in packets.
363 It is unspecified whether the payload of supported encapsulations
364 (e.g. VXLAN payload) is matched by such a pattern, which may apply to inner,
365 outer or both packets.
367 .. _table_rte_flow_invalid_l3:
369 .. table:: Invalid, missing L3
381 The above pattern is invalid due to a missing L3 specification between L2
382 (Ethernet) and L4 (UDP). Doing so is only allowed at the bottom and at the
388 They match meta-data or affect pattern processing instead of matching packet
389 data directly, most of them do not need a specification structure. This
390 particularity allows them to be specified anywhere in the stack without
391 causing any side effect.
396 End marker for item lists. Prevents further processing of items, thereby
399 - Its numeric value is 0 for convenience.
400 - PMD support is mandatory.
401 - ``spec``, ``last`` and ``mask`` are ignored.
403 .. _table_rte_flow_item_end:
407 +----------+---------+
409 +==========+=========+
410 | ``spec`` | ignored |
411 +----------+---------+
412 | ``last`` | ignored |
413 +----------+---------+
414 | ``mask`` | ignored |
415 +----------+---------+
420 Used as a placeholder for convenience. It is ignored and simply discarded by
423 - PMD support is mandatory.
424 - ``spec``, ``last`` and ``mask`` are ignored.
426 .. _table_rte_flow_item_void:
430 +----------+---------+
432 +==========+=========+
433 | ``spec`` | ignored |
434 +----------+---------+
435 | ``last`` | ignored |
436 +----------+---------+
437 | ``mask`` | ignored |
438 +----------+---------+
440 One usage example for this type is generating rules that share a common
441 prefix quickly without reallocating memory, only by updating item types:
443 .. _table_rte_flow_item_void_example:
445 .. table:: TCP, UDP or ICMP as L4
447 +-------+--------------------+
449 +=======+====================+
451 +-------+--------------------+
453 +-------+------+------+------+
454 | 2 | UDP | VOID | VOID |
455 +-------+------+------+------+
456 | 3 | VOID | TCP | VOID |
457 +-------+------+------+------+
458 | 4 | VOID | VOID | ICMP |
459 +-------+------+------+------+
461 +-------+--------------------+
466 Inverted matching, i.e. process packets that do not match the pattern.
468 - ``spec``, ``last`` and ``mask`` are ignored.
470 .. _table_rte_flow_item_invert:
474 +----------+---------+
476 +==========+=========+
477 | ``spec`` | ignored |
478 +----------+---------+
479 | ``last`` | ignored |
480 +----------+---------+
481 | ``mask`` | ignored |
482 +----------+---------+
484 Usage example, matching non-TCPv4 packets only:
486 .. _table_rte_flow_item_invert_example:
488 .. table:: Anything but TCPv4
507 Matches traffic originating from (ingress) or going to (egress) the physical
508 function of the current device.
510 If supported, should work even if the physical function is not managed by
511 the application and thus not associated with a DPDK port ID.
513 - Can be combined with any number of `Item: VF`_ to match both PF and VF
515 - ``spec``, ``last`` and ``mask`` must not be set.
517 .. _table_rte_flow_item_pf:
534 Matches traffic originating from (ingress) or going to (egress) a given
535 virtual function of the current device.
537 If supported, should work even if the virtual function is not managed by the
538 application and thus not associated with a DPDK port ID.
540 Note this pattern item does not match VF representors traffic which, as
541 separate entities, should be addressed through their own DPDK port IDs.
543 - Can be specified multiple times to match traffic addressed to several VF
545 - Can be combined with a PF item to match both PF and VF traffic.
546 - Default ``mask`` matches any VF ID.
548 .. _table_rte_flow_item_vf:
552 +----------+----------+---------------------------+
553 | Field | Subfield | Value |
554 +==========+==========+===========================+
555 | ``spec`` | ``id`` | destination VF ID |
556 +----------+----------+---------------------------+
557 | ``last`` | ``id`` | upper range value |
558 +----------+----------+---------------------------+
559 | ``mask`` | ``id`` | zeroed to match any VF ID |
560 +----------+----------+---------------------------+
565 Matches traffic originating from (ingress) or going to (egress) a physical
566 port of the underlying device.
568 The first PHY_PORT item overrides the physical port normally associated with
569 the specified DPDK input port (port_id). This item can be provided several
570 times to match additional physical ports.
572 Note that physical ports are not necessarily tied to DPDK input ports
573 (port_id) when those are not under DPDK control. Possible values are
574 specific to each device, they are not necessarily indexed from zero and may
577 As a device property, the list of allowed values as well as the value
578 associated with a port_id should be retrieved by other means.
580 - Default ``mask`` matches any port index.
582 .. _table_rte_flow_item_phy_port:
586 +----------+-----------+--------------------------------+
587 | Field | Subfield | Value |
588 +==========+===========+================================+
589 | ``spec`` | ``index`` | physical port index |
590 +----------+-----------+--------------------------------+
591 | ``last`` | ``index`` | upper range value |
592 +----------+-----------+--------------------------------+
593 | ``mask`` | ``index`` | zeroed to match any port index |
594 +----------+-----------+--------------------------------+
599 Matches traffic originating from (ingress) or going to (egress) a given DPDK
602 Normally only supported if the port ID in question is known by the
603 underlying PMD and related to the device the flow rule is created against.
605 This must not be confused with `Item: PHY_PORT`_ which refers to the
606 physical port of a device, whereas `Item: PORT_ID`_ refers to a ``struct
607 rte_eth_dev`` object on the application side (also known as "port
608 representor" depending on the kind of underlying device).
610 - Default ``mask`` matches the specified DPDK port ID.
612 .. _table_rte_flow_item_port_id:
616 +----------+----------+-----------------------------+
617 | Field | Subfield | Value |
618 +==========+==========+=============================+
619 | ``spec`` | ``id`` | DPDK port ID |
620 +----------+----------+-----------------------------+
621 | ``last`` | ``id`` | upper range value |
622 +----------+----------+-----------------------------+
623 | ``mask`` | ``id`` | zeroed to match any port ID |
624 +----------+----------+-----------------------------+
629 Matches an arbitrary integer value which was set using the ``MARK`` action in
630 a previously matched rule.
632 This item can only specified once as a match criteria as the ``MARK`` action can
633 only be specified once in a flow action.
635 Note the value of MARK field is arbitrary and application defined.
637 Depending on the underlying implementation the MARK item may be supported on
638 the physical device, with virtual groups in the PMD or not at all.
640 - Default ``mask`` matches any integer value.
642 .. _table_rte_flow_item_mark:
646 +----------+----------+---------------------------+
647 | Field | Subfield | Value |
648 +==========+==========+===========================+
649 | ``spec`` | ``id`` | integer value |
650 +----------+--------------------------------------+
651 | ``last`` | ``id`` | upper range value |
652 +----------+----------+---------------------------+
653 | ``mask`` | ``id`` | zeroed to match any value |
654 +----------+----------+---------------------------+
659 Matches tag item set by other flows. Multiple tags are supported by specifying
662 - Default ``mask`` matches the specified tag value and index.
664 .. _table_rte_flow_item_tag:
668 +----------+----------+----------------------------------------+
669 | Field | Subfield | Value |
670 +==========+===========+=======================================+
671 | ``spec`` | ``data`` | 32 bit flow tag value |
672 | +-----------+---------------------------------------+
673 | | ``index`` | index of flow tag |
674 +----------+-----------+---------------------------------------+
675 | ``last`` | ``data`` | upper range value |
676 | +-----------+---------------------------------------+
677 | | ``index`` | field is ignored |
678 +----------+-----------+---------------------------------------+
679 | ``mask`` | ``data`` | bit-mask applies to "spec" and "last" |
680 | +-----------+---------------------------------------+
681 | | ``index`` | field is ignored |
682 +----------+-----------+---------------------------------------+
687 Matches 32 bit metadata item set.
689 On egress, metadata can be set either by mbuf metadata field with
690 PKT_TX_DYNF_METADATA flag or ``SET_META`` action. On ingress, ``SET_META``
691 action sets metadata for a packet and the metadata will be reported via
692 ``metadata`` dynamic field of ``rte_mbuf`` with PKT_RX_DYNF_METADATA flag.
694 - Default ``mask`` matches the specified Rx metadata value.
696 .. _table_rte_flow_item_meta:
700 +----------+----------+---------------------------------------+
701 | Field | Subfield | Value |
702 +==========+==========+=======================================+
703 | ``spec`` | ``data`` | 32 bit metadata value |
704 +----------+----------+---------------------------------------+
705 | ``last`` | ``data`` | upper range value |
706 +----------+----------+---------------------------------------+
707 | ``mask`` | ``data`` | bit-mask applies to "spec" and "last" |
708 +----------+----------+---------------------------------------+
710 Data matching item types
711 ~~~~~~~~~~~~~~~~~~~~~~~~
713 Most of these are basically protocol header definitions with associated
714 bit-masks. They must be specified (stacked) from lowest to highest protocol
715 layer to form a matching pattern.
720 Matches any protocol in place of the current layer, a single ANY may also
721 stand for several protocol layers.
723 This is usually specified as the first pattern item when looking for a
724 protocol anywhere in a packet.
726 - Default ``mask`` stands for any number of layers.
728 .. _table_rte_flow_item_any:
732 +----------+----------+--------------------------------------+
733 | Field | Subfield | Value |
734 +==========+==========+======================================+
735 | ``spec`` | ``num`` | number of layers covered |
736 +----------+----------+--------------------------------------+
737 | ``last`` | ``num`` | upper range value |
738 +----------+----------+--------------------------------------+
739 | ``mask`` | ``num`` | zeroed to cover any number of layers |
740 +----------+----------+--------------------------------------+
742 Example for VXLAN TCP payload matching regardless of outer L3 (IPv4 or IPv6)
743 and L4 (UDP) both matched by the first ANY specification, and inner L3 (IPv4
744 or IPv6) matched by the second ANY specification:
746 .. _table_rte_flow_item_any_example:
748 .. table:: TCP in VXLAN with wildcards
750 +-------+------+----------+----------+-------+
751 | Index | Item | Field | Subfield | Value |
752 +=======+======+==========+==========+=======+
754 +-------+------+----------+----------+-------+
755 | 1 | ANY | ``spec`` | ``num`` | 2 |
756 +-------+------+----------+----------+-------+
758 +-------+------------------------------------+
760 +-------+------+----------+----------+-------+
761 | 4 | ANY | ``spec`` | ``num`` | 1 |
762 +-------+------+----------+----------+-------+
764 +-------+------------------------------------+
766 +-------+------------------------------------+
771 Matches a byte string of a given length at a given offset.
773 Offset is either absolute (using the start of the packet) or relative to the
774 end of the previous matched item in the stack, in which case negative values
777 If search is enabled, offset is used as the starting point. The search area
778 can be delimited by setting limit to a nonzero value, which is the maximum
779 number of bytes after offset where the pattern may start.
781 Matching a zero-length pattern is allowed, doing so resets the relative
782 offset for subsequent items.
784 - This type does not support ranges (``last`` field).
785 - Default ``mask`` matches all fields exactly.
787 .. _table_rte_flow_item_raw:
791 +----------+--------------+-------------------------------------------------+
792 | Field | Subfield | Value |
793 +==========+==============+=================================================+
794 | ``spec`` | ``relative`` | look for pattern after the previous item |
795 | +--------------+-------------------------------------------------+
796 | | ``search`` | search pattern from offset (see also ``limit``) |
797 | +--------------+-------------------------------------------------+
798 | | ``reserved`` | reserved, must be set to zero |
799 | +--------------+-------------------------------------------------+
800 | | ``offset`` | absolute or relative offset for ``pattern`` |
801 | +--------------+-------------------------------------------------+
802 | | ``limit`` | search area limit for start of ``pattern`` |
803 | +--------------+-------------------------------------------------+
804 | | ``length`` | ``pattern`` length |
805 | +--------------+-------------------------------------------------+
806 | | ``pattern`` | byte string to look for |
807 +----------+--------------+-------------------------------------------------+
808 | ``last`` | if specified, either all 0 or with the same values as ``spec`` |
809 +----------+----------------------------------------------------------------+
810 | ``mask`` | bit-mask applied to ``spec`` values with usual behavior |
811 +----------+----------------------------------------------------------------+
813 Example pattern looking for several strings at various offsets of a UDP
814 payload, using combined RAW items:
816 .. _table_rte_flow_item_raw_example:
818 .. table:: UDP payload matching
820 +-------+------+----------+--------------+-------+
821 | Index | Item | Field | Subfield | Value |
822 +=======+======+==========+==============+=======+
824 +-------+----------------------------------------+
826 +-------+----------------------------------------+
828 +-------+------+----------+--------------+-------+
829 | 3 | RAW | ``spec`` | ``relative`` | 1 |
830 | | | +--------------+-------+
831 | | | | ``search`` | 1 |
832 | | | +--------------+-------+
833 | | | | ``offset`` | 10 |
834 | | | +--------------+-------+
835 | | | | ``limit`` | 0 |
836 | | | +--------------+-------+
837 | | | | ``length`` | 3 |
838 | | | +--------------+-------+
839 | | | | ``pattern`` | "foo" |
840 +-------+------+----------+--------------+-------+
841 | 4 | RAW | ``spec`` | ``relative`` | 1 |
842 | | | +--------------+-------+
843 | | | | ``search`` | 0 |
844 | | | +--------------+-------+
845 | | | | ``offset`` | 20 |
846 | | | +--------------+-------+
847 | | | | ``limit`` | 0 |
848 | | | +--------------+-------+
849 | | | | ``length`` | 3 |
850 | | | +--------------+-------+
851 | | | | ``pattern`` | "bar" |
852 +-------+------+----------+--------------+-------+
853 | 5 | RAW | ``spec`` | ``relative`` | 1 |
854 | | | +--------------+-------+
855 | | | | ``search`` | 0 |
856 | | | +--------------+-------+
857 | | | | ``offset`` | -29 |
858 | | | +--------------+-------+
859 | | | | ``limit`` | 0 |
860 | | | +--------------+-------+
861 | | | | ``length`` | 3 |
862 | | | +--------------+-------+
863 | | | | ``pattern`` | "baz" |
864 +-------+------+----------+--------------+-------+
866 +-------+----------------------------------------+
870 - Locate "foo" at least 10 bytes deep inside UDP payload.
871 - Locate "bar" after "foo" plus 20 bytes.
872 - Locate "baz" after "bar" minus 29 bytes.
874 Such a packet may be represented as follows (not to scale)::
877 | |<--------->| |<--------->|
879 |-----|------|-----|-----|-----|-----|-----------|-----|------|
880 | ETH | IPv4 | UDP | ... | baz | foo | ......... | bar | .... |
881 |-----|------|-----|-----|-----|-----|-----------|-----|------|
883 |<--------------------------->|
886 Note that matching subsequent pattern items would resume after "baz", not
887 "bar" since matching is always performed after the previous item of the
893 Matches an Ethernet header.
895 The ``type`` field either stands for "EtherType" or "TPID" when followed by
896 so-called layer 2.5 pattern items such as ``RTE_FLOW_ITEM_TYPE_VLAN``. In
897 the latter case, ``type`` refers to that of the outer header, with the inner
898 EtherType/TPID provided by the subsequent pattern item. This is the same
899 order as on the wire.
900 If the ``type`` field contains a TPID value, then only tagged packets with the
901 specified TPID will match the pattern.
902 The field ``has_vlan`` can be used to match any type of tagged packets,
903 instead of using the ``type`` field.
904 If the ``type`` and ``has_vlan`` fields are not specified, then both tagged
905 and untagged packets will match the pattern.
907 - ``dst``: destination MAC.
908 - ``src``: source MAC.
909 - ``type``: EtherType or TPID.
910 - ``has_vlan``: packet header contains at least one VLAN.
911 - Default ``mask`` matches destination and source addresses only.
916 Matches an 802.1Q/ad VLAN tag.
918 The corresponding standard outer EtherType (TPID) values are
919 ``RTE_ETHER_TYPE_VLAN`` or ``RTE_ETHER_TYPE_QINQ``. It can be overridden by the
920 preceding pattern item.
921 If a ``VLAN`` item is present in the pattern, then only tagged packets will
923 The field ``has_more_vlan`` can be used to match any type of tagged packets,
924 instead of using the ``inner_type field``.
925 If the ``inner_type`` and ``has_more_vlan`` fields are not specified,
926 then any tagged packets will match the pattern.
928 - ``tci``: tag control information.
929 - ``inner_type``: inner EtherType or TPID.
930 - ``has_more_vlan``: packet header contains at least one more VLAN, after this VLAN.
931 - Default ``mask`` matches the VID part of TCI only (lower 12 bits).
936 Matches an IPv4 header.
938 Note: IPv4 options are handled by dedicated pattern items.
940 - ``hdr``: IPv4 header definition (``rte_ip.h``).
941 - Default ``mask`` matches source and destination addresses only.
946 Matches an IPv6 header.
948 Dedicated flags indicate if header contains specific extension headers.
949 To match on packets containing a specific extension header, an application
950 should match on the dedicated flag set to 1.
951 To match on packets not containing a specific extension header, an application
952 should match on the dedicated flag clear to 0.
953 In case application doesn't care about the existence of a specific extension
954 header, it should not specify the dedicated flag for matching.
956 - ``hdr``: IPv6 header definition (``rte_ip.h``).
957 - ``has_hop_ext``: header contains Hop-by-Hop Options extension header.
958 - ``has_route_ext``: header contains Routing extension header.
959 - ``has_frag_ext``: header contains Fragment extension header.
960 - ``has_auth_ext``: header contains Authentication extension header.
961 - ``has_esp_ext``: header contains Encapsulation Security Payload extension header.
962 - ``has_dest_ext``: header contains Destination Options extension header.
963 - ``has_mobil_ext``: header contains Mobility extension header.
964 - ``has_hip_ext``: header contains Host Identity Protocol extension header.
965 - ``has_shim6_ext``: header contains Shim6 Protocol extension header.
966 - Default ``mask`` matches ``hdr`` source and destination addresses only.
971 Matches an ICMP header.
973 - ``hdr``: ICMP header definition (``rte_icmp.h``).
974 - Default ``mask`` matches ICMP type and code only.
979 Matches a UDP header.
981 - ``hdr``: UDP header definition (``rte_udp.h``).
982 - Default ``mask`` matches source and destination ports only.
987 Matches a TCP header.
989 - ``hdr``: TCP header definition (``rte_tcp.h``).
990 - Default ``mask`` matches source and destination ports only.
995 Matches a SCTP header.
997 - ``hdr``: SCTP header definition (``rte_sctp.h``).
998 - Default ``mask`` matches source and destination ports only.
1003 Matches a VXLAN header (RFC 7348).
1005 - ``flags``: normally 0x08 (I flag).
1006 - ``rsvd0``: reserved, normally 0x000000.
1007 - ``vni``: VXLAN network identifier.
1008 - ``rsvd1``: reserved, normally 0x00.
1009 - Default ``mask`` matches VNI only.
1014 Matches an IEEE 802.1BR E-Tag header.
1016 The corresponding standard outer EtherType (TPID) value is
1017 ``RTE_ETHER_TYPE_ETAG``. It can be overridden by the preceding pattern item.
1019 - ``epcp_edei_in_ecid_b``: E-Tag control information (E-TCI), E-PCP (3b),
1020 E-DEI (1b), ingress E-CID base (12b).
1021 - ``rsvd_grp_ecid_b``: reserved (2b), GRP (2b), E-CID base (12b).
1022 - ``in_ecid_e``: ingress E-CID ext.
1023 - ``ecid_e``: E-CID ext.
1024 - ``inner_type``: inner EtherType or TPID.
1025 - Default ``mask`` simultaneously matches GRP and E-CID base.
1030 Matches a NVGRE header (RFC 7637).
1032 - ``c_k_s_rsvd0_ver``: checksum (1b), undefined (1b), key bit (1b),
1033 sequence number (1b), reserved 0 (9b), version (3b). This field must have
1034 value 0x2000 according to RFC 7637.
1035 - ``protocol``: protocol type (0x6558).
1036 - ``tni``: virtual subnet ID.
1037 - ``flow_id``: flow ID.
1038 - Default ``mask`` matches TNI only.
1043 Matches a MPLS header.
1045 - ``label_tc_s_ttl``: label, TC, Bottom of Stack and TTL.
1046 - Default ``mask`` matches label only.
1051 Matches a GRE header.
1053 - ``c_rsvd0_ver``: checksum, reserved 0 and version.
1054 - ``protocol``: protocol type.
1055 - Default ``mask`` matches protocol only.
1060 Matches a GRE key field.
1061 This should be preceded by item ``GRE``.
1063 - Value to be matched is a big-endian 32 bit integer.
1064 - When this item present it implicitly match K bit in default mask as "1"
1069 Fuzzy pattern match, expect faster than default.
1071 This is for device that support fuzzy match option. Usually a fuzzy match is
1072 fast but the cost is accuracy. i.e. Signature Match only match pattern's hash
1073 value, but it is possible two different patterns have the same hash value.
1075 Matching accuracy level can be configured by threshold. Driver can divide the
1076 range of threshold and map to different accuracy levels that device support.
1078 Threshold 0 means perfect match (no fuzziness), while threshold 0xffffffff
1079 means fuzziest match.
1081 .. _table_rte_flow_item_fuzzy:
1085 +----------+---------------+--------------------------------------------------+
1086 | Field | Subfield | Value |
1087 +==========+===============+==================================================+
1088 | ``spec`` | ``threshold`` | 0 as perfect match, 0xffffffff as fuzziest match |
1089 +----------+---------------+--------------------------------------------------+
1090 | ``last`` | ``threshold`` | upper range value |
1091 +----------+---------------+--------------------------------------------------+
1092 | ``mask`` | ``threshold`` | bit-mask apply to "spec" and "last" |
1093 +----------+---------------+--------------------------------------------------+
1095 Usage example, fuzzy match a TCPv4 packets:
1097 .. _table_rte_flow_item_fuzzy_example:
1099 .. table:: Fuzzy matching
1101 +-------+----------+
1103 +=======+==========+
1105 +-------+----------+
1107 +-------+----------+
1109 +-------+----------+
1111 +-------+----------+
1113 +-------+----------+
1115 Item: ``GTP``, ``GTPC``, ``GTPU``
1116 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1118 Matches a GTPv1 header.
1120 Note: GTP, GTPC and GTPU use the same structure. GTPC and GTPU item
1121 are defined for a user-friendly API when creating GTP-C and GTP-U
1124 - ``v_pt_rsv_flags``: version (3b), protocol type (1b), reserved (1b),
1125 extension header flag (1b), sequence number flag (1b), N-PDU number
1127 - ``msg_type``: message type.
1128 - ``msg_len``: message length.
1129 - ``teid``: tunnel endpoint identifier.
1130 - Default ``mask`` matches teid only.
1135 Matches an ESP header.
1137 - ``hdr``: ESP header definition (``rte_esp.h``).
1138 - Default ``mask`` matches SPI only.
1143 Matches a GENEVE header.
1145 - ``ver_opt_len_o_c_rsvd0``: version (2b), length of the options fields (6b),
1146 OAM packet (1b), critical options present (1b), reserved 0 (6b).
1147 - ``protocol``: protocol type.
1148 - ``vni``: virtual network identifier.
1149 - ``rsvd1``: reserved, normally 0x00.
1150 - Default ``mask`` matches VNI only.
1155 Matches a VXLAN-GPE header (draft-ietf-nvo3-vxlan-gpe-05).
1157 - ``flags``: normally 0x0C (I and P flags).
1158 - ``rsvd0``: reserved, normally 0x0000.
1159 - ``protocol``: protocol type.
1160 - ``vni``: VXLAN network identifier.
1161 - ``rsvd1``: reserved, normally 0x00.
1162 - Default ``mask`` matches VNI only.
1164 Item: ``ARP_ETH_IPV4``
1165 ^^^^^^^^^^^^^^^^^^^^^^
1167 Matches an ARP header for Ethernet/IPv4.
1169 - ``hdr``: hardware type, normally 1.
1170 - ``pro``: protocol type, normally 0x0800.
1171 - ``hln``: hardware address length, normally 6.
1172 - ``pln``: protocol address length, normally 4.
1173 - ``op``: opcode (1 for request, 2 for reply).
1174 - ``sha``: sender hardware address.
1175 - ``spa``: sender IPv4 address.
1176 - ``tha``: target hardware address.
1177 - ``tpa``: target IPv4 address.
1178 - Default ``mask`` matches SHA, SPA, THA and TPA.
1183 Matches the presence of any IPv6 extension header.
1185 - ``next_hdr``: next header.
1186 - Default ``mask`` matches ``next_hdr``.
1188 Normally preceded by any of:
1193 Item: ``IPV6_FRAG_EXT``
1194 ^^^^^^^^^^^^^^^^^^^^^^^
1196 Matches the presence of IPv6 fragment extension header.
1198 - ``hdr``: IPv6 fragment extension header definition (``rte_ip.h``).
1200 Normally preceded by any of:
1208 Matches any ICMPv6 header.
1210 - ``type``: ICMPv6 type.
1211 - ``code``: ICMPv6 code.
1212 - ``checksum``: ICMPv6 checksum.
1213 - Default ``mask`` matches ``type`` and ``code``.
1215 Item: ``ICMP6_ND_NS``
1216 ^^^^^^^^^^^^^^^^^^^^^
1218 Matches an ICMPv6 neighbor discovery solicitation.
1220 - ``type``: ICMPv6 type, normally 135.
1221 - ``code``: ICMPv6 code, normally 0.
1222 - ``checksum``: ICMPv6 checksum.
1223 - ``reserved``: reserved, normally 0.
1224 - ``target_addr``: target address.
1225 - Default ``mask`` matches target address only.
1227 Item: ``ICMP6_ND_NA``
1228 ^^^^^^^^^^^^^^^^^^^^^
1230 Matches an ICMPv6 neighbor discovery advertisement.
1232 - ``type``: ICMPv6 type, normally 136.
1233 - ``code``: ICMPv6 code, normally 0.
1234 - ``checksum``: ICMPv6 checksum.
1235 - ``rso_reserved``: route flag (1b), solicited flag (1b), override flag
1236 (1b), reserved (29b).
1237 - ``target_addr``: target address.
1238 - Default ``mask`` matches target address only.
1240 Item: ``ICMP6_ND_OPT``
1241 ^^^^^^^^^^^^^^^^^^^^^^
1243 Matches the presence of any ICMPv6 neighbor discovery option.
1245 - ``type``: ND option type.
1246 - ``length``: ND option length.
1247 - Default ``mask`` matches type only.
1249 Normally preceded by any of:
1251 - `Item: ICMP6_ND_NA`_
1252 - `Item: ICMP6_ND_NS`_
1253 - `Item: ICMP6_ND_OPT`_
1255 Item: ``ICMP6_ND_OPT_SLA_ETH``
1256 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1258 Matches an ICMPv6 neighbor discovery source Ethernet link-layer address
1261 - ``type``: ND option type, normally 1.
1262 - ``length``: ND option length, normally 1.
1263 - ``sla``: source Ethernet LLA.
1264 - Default ``mask`` matches source link-layer address only.
1266 Normally preceded by any of:
1268 - `Item: ICMP6_ND_NA`_
1269 - `Item: ICMP6_ND_OPT`_
1271 Item: ``ICMP6_ND_OPT_TLA_ETH``
1272 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1274 Matches an ICMPv6 neighbor discovery target Ethernet link-layer address
1277 - ``type``: ND option type, normally 2.
1278 - ``length``: ND option length, normally 1.
1279 - ``tla``: target Ethernet LLA.
1280 - Default ``mask`` matches target link-layer address only.
1282 Normally preceded by any of:
1284 - `Item: ICMP6_ND_NS`_
1285 - `Item: ICMP6_ND_OPT`_
1290 Matches an application specific 32 bit metadata item.
1292 - Default ``mask`` matches the specified metadata value.
1297 Matches a GTP PDU extension header with type 0x85.
1299 - ``pdu_type``: PDU type.
1300 - ``qfi``: QoS flow identifier.
1301 - Default ``mask`` matches QFI only.
1303 Item: ``PPPOES``, ``PPPOED``
1304 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1306 Matches a PPPoE header.
1308 - ``version_type``: version (4b), type (4b).
1309 - ``code``: message type.
1310 - ``session_id``: session identifier.
1311 - ``length``: payload length.
1313 Item: ``PPPOE_PROTO_ID``
1314 ^^^^^^^^^^^^^^^^^^^^^^^^
1316 Matches a PPPoE session protocol identifier.
1318 - ``proto_id``: PPP protocol identifier.
1319 - Default ``mask`` matches proto_id only.
1324 Matches a network service header (RFC 8300).
1326 - ``version``: normally 0x0 (2 bits).
1327 - ``oam_pkt``: indicate oam packet (1 bit).
1328 - ``reserved``: reserved bit (1 bit).
1329 - ``ttl``: maximum SFF hopes (6 bits).
1330 - ``length``: total length in 4 bytes words (6 bits).
1331 - ``reserved1``: reserved1 bits (4 bits).
1332 - ``mdtype``: ndicates format of NSH header (4 bits).
1333 - ``next_proto``: indicates protocol type of encap data (8 bits).
1334 - ``spi``: service path identifier (3 bytes).
1335 - ``sindex``: service index (1 byte).
1336 - Default ``mask`` matches mdtype, next_proto, spi, sindex.
1342 Matches a Internet Group Management Protocol (RFC 2236).
1344 - ``type``: IGMP message type (Query/Report).
1345 - ``max_resp_time``: max time allowed before sending report.
1346 - ``checksum``: checksum, 1s complement of whole IGMP message.
1347 - ``group_addr``: group address, for Query value will be 0.
1348 - Default ``mask`` matches group_addr.
1354 Matches a IP Authentication Header (RFC 4302).
1356 - ``next_hdr``: next payload after AH.
1357 - ``payload_len``: total length of AH in 4B words.
1358 - ``reserved``: reserved bits.
1359 - ``spi``: security parameters index.
1360 - ``seq_num``: counter value increased by 1 on each packet sent.
1361 - Default ``mask`` matches spi.
1366 Matches a HIGIG2 header field. It is layer 2.5 protocol and used in
1369 - Default ``mask`` matches classification and vlan.
1374 Matches a L2TPv3 over IP header.
1376 - ``session_id``: L2TPv3 over IP session identifier.
1377 - Default ``mask`` matches session_id only.
1382 Matches a PFCP Header.
1384 - ``s_field``: S field.
1385 - ``msg_type``: message type.
1386 - ``msg_len``: message length.
1387 - ``seid``: session endpoint identifier.
1388 - Default ``mask`` matches s_field and seid.
1393 Matches a eCPRI header.
1395 - ``hdr``: eCPRI header definition (``rte_ecpri.h``).
1396 - Default ``mask`` matches nothing, for all eCPRI messages.
1398 Item: ``PACKET_INTEGRITY_CHECKS``
1399 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1401 Matches packet integrity.
1402 For some devices application needs to enable integration checks in HW
1403 before using this item.
1405 - ``level``: the encapsulation level that should be checked:
1406 - ``level == 0`` means the default PMD mode (can be inner most / outermost).
1407 - ``level == 1`` means outermost header.
1408 - ``level > 1`` means inner header. See also RSS level.
1409 - ``packet_ok``: All HW packet integrity checks have passed based on the
1410 topmost network layer. For example, for ICMP packet the topmost network
1411 layer is L3 and for TCP or UDP packet the topmost network layer is L4.
1412 - ``l2_ok``: all layer 2 HW integrity checks passed.
1413 - ``l3_ok``: all layer 3 HW integrity checks passed.
1414 - ``l4_ok``: all layer 4 HW integrity checks passed.
1415 - ``l2_crc_ok``: layer 2 CRC check passed.
1416 - ``ipv4_csum_ok``: IPv4 checksum check passed.
1417 - ``l4_csum_ok``: layer 4 checksum check passed.
1418 - ``l3_len_ok``: the layer 3 length is smaller than the frame length.
1423 Matches a conntrack state after conntrack action.
1425 - ``flags``: conntrack packet state flags.
1426 - Default ``mask`` matches all state bits.
1428 Item: ``PORT_REPRESENTOR``
1429 ^^^^^^^^^^^^^^^^^^^^^^^^^^
1431 Matches traffic entering the embedded switch from the given ethdev.
1433 Term **ethdev** and the concept of **port representor** are synonymous.
1434 The **represented port** is an *entity* plugged to the embedded switch
1435 at the opposite end of the "wire" leading to the ethdev.
1439 .--------------------.
1440 | PORT_REPRESENTOR | Ethdev (Application Port Referred to by its ID)
1441 '--------------------'
1463 .--------------------.
1464 | REPRESENTED_PORT | Net / Guest / Another Ethdev (Same Application)
1465 '--------------------'
1468 - Incompatible with `Attribute: Traffic direction`_.
1469 - Requires `Attribute: Transfer`_.
1471 .. _table_rte_flow_item_ethdev:
1473 .. table:: ``struct rte_flow_item_ethdev``
1475 +----------+-------------+---------------------------+
1476 | Field | Subfield | Value |
1477 +==========+=============+===========================+
1478 | ``spec`` | ``port_id`` | ethdev port ID |
1479 +----------+-------------+---------------------------+
1480 | ``last`` | ``port_id`` | upper range value |
1481 +----------+-------------+---------------------------+
1482 | ``mask`` | ``port_id`` | zeroed for wildcard match |
1483 +----------+-------------+---------------------------+
1485 - Default ``mask`` provides exact match behaviour.
1487 Item: ``REPRESENTED_PORT``
1488 ^^^^^^^^^^^^^^^^^^^^^^^^^^
1490 Matches traffic entering the embedded switch from
1491 the entity represented by the given ethdev.
1493 Term **ethdev** and the concept of **port representor** are synonymous.
1494 The **represented port** is an *entity* plugged to the embedded switch
1495 at the opposite end of the "wire" leading to the ethdev.
1499 .--------------------.
1500 | PORT_REPRESENTOR | Ethdev (Application Port Referred to by its ID)
1501 '--------------------'
1523 .--------------------.
1524 | REPRESENTED_PORT | Net / Guest / Another Ethdev (Same Application)
1525 '--------------------'
1528 - Incompatible with `Attribute: Traffic direction`_.
1529 - Requires `Attribute: Transfer`_.
1531 This item is meant to use the same structure as `Item: PORT_REPRESENTOR`_.
1536 Each possible action is represented by a type.
1537 An action can have an associated configuration object.
1538 Several actions combined in a list can be assigned
1539 to a flow rule and are performed in order.
1541 They fall in three categories:
1543 - Actions that modify the fate of matching traffic, for instance by dropping
1544 or assigning it a specific destination.
1546 - Actions that modify matching traffic contents or its properties. This
1547 includes adding/removing encapsulation, encryption, compression and marks.
1549 - Actions related to the flow rule itself, such as updating counters or
1550 making it non-terminating.
1552 Flow rules being terminating by default, not specifying any action of the
1553 fate kind results in undefined behavior. This applies to both ingress and
1556 PASSTHRU, when supported, makes a flow rule non-terminating.
1558 Like matching patterns, action lists are terminated by END items.
1560 Example of action that redirects packets to queue index 10:
1562 .. _table_rte_flow_action_example:
1564 .. table:: Queue action
1566 +-----------+-------+
1568 +===========+=======+
1570 +-----------+-------+
1572 Actions are performed in list order:
1574 .. _table_rte_flow_count_then_drop:
1576 .. table:: Count then drop
1590 .. _table_rte_flow_mark_count_redirect:
1592 .. table:: Mark, count then redirect
1594 +-------+--------+------------+-------+
1595 | Index | Action | Field | Value |
1596 +=======+========+============+=======+
1597 | 0 | MARK | ``mark`` | 0x2a |
1598 +-------+--------+------------+-------+
1599 | 1 | COUNT | ``id`` | 0 |
1600 +-------+--------+------------+-------+
1601 | 2 | QUEUE | ``queue`` | 10 |
1602 +-------+--------+------------+-------+
1604 +-------+-----------------------------+
1608 .. _table_rte_flow_redirect_queue_5:
1610 .. table:: Redirect to queue 5
1612 +-------+--------+-----------+-------+
1613 | Index | Action | Field | Value |
1614 +=======+========+===========+=======+
1616 +-------+--------+-----------+-------+
1617 | 1 | QUEUE | ``queue`` | 5 |
1618 +-------+--------+-----------+-------+
1620 +-------+----------------------------+
1622 In the above example, while DROP and QUEUE must be performed in order, both
1623 have to happen before reaching END. Only QUEUE has a visible effect.
1625 Note that such a list may be thought as ambiguous and rejected on that
1628 .. _table_rte_flow_redirect_queue_5_3:
1630 .. table:: Redirect to queues 5 and 3
1632 +-------+--------+-----------+-------+
1633 | Index | Action | Field | Value |
1634 +=======+========+===========+=======+
1635 | 0 | QUEUE | ``queue`` | 5 |
1636 +-------+--------+-----------+-------+
1638 +-------+--------+-----------+-------+
1639 | 2 | QUEUE | ``queue`` | 3 |
1640 +-------+--------+-----------+-------+
1642 +-------+----------------------------+
1644 As previously described, all actions must be taken into account. This
1645 effectively duplicates traffic to both queues. The above example also shows
1646 that VOID is ignored.
1651 Common action types are described in this section.
1656 End marker for action lists. Prevents further processing of actions, thereby
1659 - Its numeric value is 0 for convenience.
1660 - PMD support is mandatory.
1661 - No configurable properties.
1663 .. _table_rte_flow_action_end:
1676 Used as a placeholder for convenience. It is ignored and simply discarded by
1679 - PMD support is mandatory.
1680 - No configurable properties.
1682 .. _table_rte_flow_action_void:
1692 Action: ``PASSTHRU``
1693 ^^^^^^^^^^^^^^^^^^^^
1695 Leaves traffic up for additional processing by subsequent flow rules; makes
1696 a flow rule non-terminating.
1698 - No configurable properties.
1700 .. _table_rte_flow_action_passthru:
1710 Example to copy a packet to a queue and continue processing by subsequent
1713 .. _table_rte_flow_action_passthru_example:
1715 .. table:: Copy to queue 8
1717 +-------+--------+-----------+-------+
1718 | Index | Action | Field | Value |
1719 +=======+========+===========+=======+
1721 +-------+--------+-----------+-------+
1722 | 1 | QUEUE | ``queue`` | 8 |
1723 +-------+--------+-----------+-------+
1725 +-------+----------------------------+
1730 Redirects packets to a group on the current device.
1732 In a hierarchy of groups, which can be used to represent physical or logical
1733 flow group/tables on the device, this action redirects the matched flow to
1734 the specified group on that device.
1736 If a matched flow is redirected to a table which doesn't contain a matching
1737 rule for that flow then the behavior is undefined and the resulting behavior
1738 is up to the specific device. Best practice when using groups would be define
1739 a default flow rule for each group which a defines the default actions in that
1740 group so a consistent behavior is defined.
1742 Defining an action for matched flow in a group to jump to a group which is
1743 higher in the group hierarchy may not be supported by physical devices,
1744 depending on how groups are mapped to the physical devices. In the
1745 definitions of jump actions, applications should be aware that it may be
1746 possible to define flow rules which trigger an undefined behavior causing
1747 flows to loop between groups.
1749 .. _table_rte_flow_action_jump:
1753 +-----------+------------------------------+
1755 +===========+==============================+
1756 | ``group`` | Group to redirect packets to |
1757 +-----------+------------------------------+
1762 Attaches an integer value to packets and sets ``PKT_RX_FDIR`` and
1763 ``PKT_RX_FDIR_ID`` mbuf flags.
1765 This value is arbitrary and application-defined. Maximum allowed value
1766 depends on the underlying implementation. It is returned in the
1767 ``hash.fdir.hi`` mbuf field.
1769 .. _table_rte_flow_action_mark:
1773 +--------+--------------------------------------+
1775 +========+======================================+
1776 | ``id`` | integer value to return with packets |
1777 +--------+--------------------------------------+
1782 Flags packets. Similar to `Action: MARK`_ without a specific value; only
1783 sets the ``PKT_RX_FDIR`` mbuf flag.
1785 - No configurable properties.
1787 .. _table_rte_flow_action_flag:
1800 Assigns packets to a given queue index.
1802 .. _table_rte_flow_action_queue:
1806 +-----------+--------------------+
1808 +===========+====================+
1809 | ``index`` | queue index to use |
1810 +-----------+--------------------+
1817 - No configurable properties.
1819 .. _table_rte_flow_action_drop:
1832 Adds a counter action to a matched flow.
1834 If more than one count action is specified in a single flow rule, then each
1835 action must specify a unique id.
1837 Counters can be retrieved and reset through ``rte_flow_query()``, see
1838 ``struct rte_flow_query_count``.
1840 For ports within the same switch domain then the counter id namespace extends
1841 to all ports within that switch domain.
1843 .. _table_rte_flow_action_count:
1847 +------------+---------------------------------+
1849 +============+=================================+
1850 | ``id`` | counter id |
1851 +------------+---------------------------------+
1853 Query structure to retrieve and reset flow rule counters:
1855 .. _table_rte_flow_query_count:
1857 .. table:: COUNT query
1859 +---------------+-----+-----------------------------------+
1860 | Field | I/O | Value |
1861 +===============+=====+===================================+
1862 | ``reset`` | in | reset counter after query |
1863 +---------------+-----+-----------------------------------+
1864 | ``hits_set`` | out | ``hits`` field is set |
1865 +---------------+-----+-----------------------------------+
1866 | ``bytes_set`` | out | ``bytes`` field is set |
1867 +---------------+-----+-----------------------------------+
1868 | ``hits`` | out | number of hits for this rule |
1869 +---------------+-----+-----------------------------------+
1870 | ``bytes`` | out | number of bytes through this rule |
1871 +---------------+-----+-----------------------------------+
1876 Similar to QUEUE, except RSS is additionally performed on packets to spread
1877 them among several queues according to the provided parameters.
1879 Unlike global RSS settings used by other DPDK APIs, unsetting the ``types``
1880 field does not disable RSS in a flow rule. Doing so instead requests safe
1881 unspecified "best-effort" settings from the underlying PMD, which depending
1882 on the flow rule, may result in anything ranging from empty (single queue)
1883 to all-inclusive RSS.
1885 If non-applicable for matching packets RSS types are requested,
1886 these RSS types are simply ignored. For example, it happens if:
1888 - Hashing of both TCP and UDP ports is requested
1889 (only one can be present in a packet).
1891 - Requested RSS types contradict to flow rule pattern
1892 (e.g. pattern has UDP item, but RSS types contain TCP).
1894 If requested RSS hash types are not supported by the Ethernet device at all
1895 (not reported in ``dev_info.flow_type_rss_offloads``),
1896 the flow creation will fail.
1898 Note: RSS hash result is stored in the ``hash.rss`` mbuf field which
1899 overlaps ``hash.fdir.lo``. Since `Action: MARK`_ sets the ``hash.fdir.hi``
1900 field only, both can be requested simultaneously.
1902 Also, regarding packet encapsulation ``level``:
1904 - ``0`` requests the default behavior. Depending on the packet type, it can
1905 mean outermost, innermost, anything in between or even no RSS.
1907 It basically stands for the innermost encapsulation level RSS can be
1908 performed on according to PMD and device capabilities.
1910 - ``1`` requests RSS to be performed on the outermost packet encapsulation
1913 - ``2`` and subsequent values request RSS to be performed on the specified
1914 inner packet encapsulation level, from outermost to innermost (lower to
1917 Values other than ``0`` are not necessarily supported.
1919 Requesting a specific RSS level on unrecognized traffic results in undefined
1920 behavior. For predictable results, it is recommended to make the flow rule
1921 pattern match packet headers up to the requested encapsulation level so that
1922 only matching traffic goes through.
1924 .. _table_rte_flow_action_rss:
1928 +---------------+---------------------------------------------+
1930 +===============+=============================================+
1931 | ``func`` | RSS hash function to apply |
1932 +---------------+---------------------------------------------+
1933 | ``level`` | encapsulation level for ``types`` |
1934 +---------------+---------------------------------------------+
1935 | ``types`` | specific RSS hash types (see ``ETH_RSS_*``) |
1936 +---------------+---------------------------------------------+
1937 | ``key_len`` | hash key length in bytes |
1938 +---------------+---------------------------------------------+
1939 | ``queue_num`` | number of entries in ``queue`` |
1940 +---------------+---------------------------------------------+
1941 | ``key`` | hash key |
1942 +---------------+---------------------------------------------+
1943 | ``queue`` | queue indices to use |
1944 +---------------+---------------------------------------------+
1949 Directs matching traffic to the physical function (PF) of the current
1954 - No configurable properties.
1956 .. _table_rte_flow_action_pf:
1969 Directs matching traffic to a given virtual function of the current device.
1971 Packets matched by a VF pattern item can be redirected to their original VF
1972 ID instead of the specified one. This parameter may not be available and is
1973 not guaranteed to work properly if the VF part is matched by a prior flow
1974 rule or if packets are not addressed to a VF in the first place.
1978 .. _table_rte_flow_action_vf:
1982 +--------------+--------------------------------+
1984 +==============+================================+
1985 | ``original`` | use original VF ID if possible |
1986 +--------------+--------------------------------+
1988 +--------------+--------------------------------+
1990 Action: ``PHY_PORT``
1991 ^^^^^^^^^^^^^^^^^^^^
1993 Directs matching traffic to a given physical port index of the underlying
1996 See `Item: PHY_PORT`_.
1998 .. _table_rte_flow_action_phy_port:
2002 +--------------+-------------------------------------+
2004 +==============+=====================================+
2005 | ``original`` | use original port index if possible |
2006 +--------------+-------------------------------------+
2007 | ``index`` | physical port index |
2008 +--------------+-------------------------------------+
2012 Directs matching traffic to a given DPDK port ID.
2014 See `Item: PORT_ID`_.
2016 .. _table_rte_flow_action_port_id:
2020 +--------------+---------------------------------------+
2022 +==============+=======================================+
2023 | ``original`` | use original DPDK port ID if possible |
2024 +--------------+---------------------------------------+
2025 | ``id`` | DPDK port ID |
2026 +--------------+---------------------------------------+
2031 Applies a stage of metering and policing.
2033 The metering and policing (MTR) object has to be first created using the
2034 rte_mtr_create() API function. The ID of the MTR object is specified as
2035 action parameter. More than one flow can use the same MTR object through
2036 the meter action. The MTR object can be further updated or queried using
2039 .. _table_rte_flow_action_meter:
2043 +--------------+---------------+
2045 +==============+===============+
2046 | ``mtr_id`` | MTR object ID |
2047 +--------------+---------------+
2049 Action: ``SECURITY``
2050 ^^^^^^^^^^^^^^^^^^^^
2052 Perform the security action on flows matched by the pattern items
2053 according to the configuration of the security session.
2055 This action modifies the payload of matched flows. For INLINE_CRYPTO, the
2056 security protocol headers and IV are fully provided by the application as
2057 specified in the flow pattern. The payload of matching packets is
2058 encrypted on egress, and decrypted and authenticated on ingress.
2059 For INLINE_PROTOCOL, the security protocol is fully offloaded to HW,
2060 providing full encapsulation and decapsulation of packets in security
2061 protocols. The flow pattern specifies both the outer security header fields
2062 and the inner packet fields. The security session specified in the action
2063 must match the pattern parameters.
2065 The security session specified in the action must be created on the same
2066 port as the flow action that is being specified.
2068 The ingress/egress flow attribute should match that specified in the
2069 security session if the security session supports the definition of the
2072 Multiple flows can be configured to use the same security session.
2074 .. _table_rte_flow_action_security:
2078 +----------------------+--------------------------------------+
2080 +======================+======================================+
2081 | ``security_session`` | security session to apply |
2082 +----------------------+--------------------------------------+
2084 The following is an example of configuring IPsec inline using the
2085 INLINE_CRYPTO security session:
2087 The encryption algorithm, keys and salt are part of the opaque
2088 ``rte_security_session``. The SA is identified according to the IP and ESP
2089 fields in the pattern items.
2091 .. _table_rte_flow_item_esp_inline_example:
2093 .. table:: IPsec inline crypto flow pattern items.
2095 +-------+----------+
2097 +=======+==========+
2099 +-------+----------+
2101 +-------+----------+
2103 +-------+----------+
2105 +-------+----------+
2107 .. _table_rte_flow_action_esp_inline_example:
2109 .. table:: IPsec inline flow actions.
2111 +-------+----------+
2113 +=======+==========+
2115 +-------+----------+
2117 +-------+----------+
2119 Action: ``OF_SET_MPLS_TTL``
2120 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2122 Implements ``OFPAT_SET_MPLS_TTL`` ("MPLS TTL") as defined by the `OpenFlow
2123 Switch Specification`_.
2125 .. _table_rte_flow_action_of_set_mpls_ttl:
2127 .. table:: OF_SET_MPLS_TTL
2129 +--------------+----------+
2131 +==============+==========+
2132 | ``mpls_ttl`` | MPLS TTL |
2133 +--------------+----------+
2135 Action: ``OF_DEC_MPLS_TTL``
2136 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2138 Implements ``OFPAT_DEC_MPLS_TTL`` ("decrement MPLS TTL") as defined by the
2139 `OpenFlow Switch Specification`_.
2141 .. _table_rte_flow_action_of_dec_mpls_ttl:
2143 .. table:: OF_DEC_MPLS_TTL
2151 Action: ``OF_SET_NW_TTL``
2152 ^^^^^^^^^^^^^^^^^^^^^^^^^
2154 Implements ``OFPAT_SET_NW_TTL`` ("IP TTL") as defined by the `OpenFlow
2155 Switch Specification`_.
2157 .. _table_rte_flow_action_of_set_nw_ttl:
2159 .. table:: OF_SET_NW_TTL
2161 +------------+--------+
2163 +============+========+
2164 | ``nw_ttl`` | IP TTL |
2165 +------------+--------+
2167 Action: ``OF_DEC_NW_TTL``
2168 ^^^^^^^^^^^^^^^^^^^^^^^^^
2170 Implements ``OFPAT_DEC_NW_TTL`` ("decrement IP TTL") as defined by the
2171 `OpenFlow Switch Specification`_.
2173 .. _table_rte_flow_action_of_dec_nw_ttl:
2175 .. table:: OF_DEC_NW_TTL
2183 Action: ``OF_COPY_TTL_OUT``
2184 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2186 Implements ``OFPAT_COPY_TTL_OUT`` ("copy TTL "outwards" -- from
2187 next-to-outermost to outermost") as defined by the `OpenFlow Switch
2190 .. _table_rte_flow_action_of_copy_ttl_out:
2192 .. table:: OF_COPY_TTL_OUT
2200 Action: ``OF_COPY_TTL_IN``
2201 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2203 Implements ``OFPAT_COPY_TTL_IN`` ("copy TTL "inwards" -- from outermost to
2204 next-to-outermost") as defined by the `OpenFlow Switch Specification`_.
2206 .. _table_rte_flow_action_of_copy_ttl_in:
2208 .. table:: OF_COPY_TTL_IN
2216 Action: ``OF_POP_VLAN``
2217 ^^^^^^^^^^^^^^^^^^^^^^^
2219 Implements ``OFPAT_POP_VLAN`` ("pop the outer VLAN tag") as defined
2220 by the `OpenFlow Switch Specification`_.
2222 .. _table_rte_flow_action_of_pop_vlan:
2224 .. table:: OF_POP_VLAN
2232 Action: ``OF_PUSH_VLAN``
2233 ^^^^^^^^^^^^^^^^^^^^^^^^
2235 Implements ``OFPAT_PUSH_VLAN`` ("push a new VLAN tag") as defined by the
2236 `OpenFlow Switch Specification`_.
2238 .. _table_rte_flow_action_of_push_vlan:
2240 .. table:: OF_PUSH_VLAN
2242 +---------------+-----------+
2244 +===============+===========+
2245 | ``ethertype`` | EtherType |
2246 +---------------+-----------+
2248 Action: ``OF_SET_VLAN_VID``
2249 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2251 Implements ``OFPAT_SET_VLAN_VID`` ("set the 802.1q VLAN id") as defined by
2252 the `OpenFlow Switch Specification`_.
2254 .. _table_rte_flow_action_of_set_vlan_vid:
2256 .. table:: OF_SET_VLAN_VID
2258 +--------------+---------+
2260 +==============+=========+
2261 | ``vlan_vid`` | VLAN id |
2262 +--------------+---------+
2264 Action: ``OF_SET_VLAN_PCP``
2265 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2267 Implements ``OFPAT_SET_LAN_PCP`` ("set the 802.1q priority") as defined by
2268 the `OpenFlow Switch Specification`_.
2270 .. _table_rte_flow_action_of_set_vlan_pcp:
2272 .. table:: OF_SET_VLAN_PCP
2274 +--------------+---------------+
2276 +==============+===============+
2277 | ``vlan_pcp`` | VLAN priority |
2278 +--------------+---------------+
2280 Action: ``OF_POP_MPLS``
2281 ^^^^^^^^^^^^^^^^^^^^^^^
2283 Implements ``OFPAT_POP_MPLS`` ("pop the outer MPLS tag") as defined by the
2284 `OpenFlow Switch Specification`_.
2286 .. _table_rte_flow_action_of_pop_mpls:
2288 .. table:: OF_POP_MPLS
2290 +---------------+-----------+
2292 +===============+===========+
2293 | ``ethertype`` | EtherType |
2294 +---------------+-----------+
2296 Action: ``OF_PUSH_MPLS``
2297 ^^^^^^^^^^^^^^^^^^^^^^^^
2299 Implements ``OFPAT_PUSH_MPLS`` ("push a new MPLS tag") as defined by the
2300 `OpenFlow Switch Specification`_.
2302 .. _table_rte_flow_action_of_push_mpls:
2304 .. table:: OF_PUSH_MPLS
2306 +---------------+-----------+
2308 +===============+===========+
2309 | ``ethertype`` | EtherType |
2310 +---------------+-----------+
2312 Action: ``VXLAN_ENCAP``
2313 ^^^^^^^^^^^^^^^^^^^^^^^
2315 Performs a VXLAN encapsulation action by encapsulating the matched flow in the
2316 VXLAN tunnel as defined in the``rte_flow_action_vxlan_encap`` flow items
2319 This action modifies the payload of matched flows. The flow definition specified
2320 in the ``rte_flow_action_tunnel_encap`` action structure must define a valid
2321 VLXAN network overlay which conforms with RFC 7348 (Virtual eXtensible Local
2322 Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks
2323 over Layer 3 Networks). The pattern must be terminated with the
2324 RTE_FLOW_ITEM_TYPE_END item type.
2326 .. _table_rte_flow_action_vxlan_encap:
2328 .. table:: VXLAN_ENCAP
2330 +----------------+-------------------------------------+
2332 +================+=====================================+
2333 | ``definition`` | Tunnel end-point overlay definition |
2334 +----------------+-------------------------------------+
2336 .. _table_rte_flow_action_vxlan_encap_example:
2338 .. table:: IPv4 VxLAN flow pattern example.
2340 +-------+----------+
2342 +=======+==========+
2344 +-------+----------+
2346 +-------+----------+
2348 +-------+----------+
2350 +-------+----------+
2352 +-------+----------+
2354 Action: ``VXLAN_DECAP``
2355 ^^^^^^^^^^^^^^^^^^^^^^^
2357 Performs a decapsulation action by stripping all headers of the VXLAN tunnel
2358 network overlay from the matched flow.
2360 The flow items pattern defined for the flow rule with which a ``VXLAN_DECAP``
2361 action is specified, must define a valid VXLAN tunnel as per RFC7348. If the
2362 flow pattern does not specify a valid VXLAN tunnel then a
2363 RTE_FLOW_ERROR_TYPE_ACTION error should be returned.
2365 This action modifies the payload of matched flows.
2367 Action: ``NVGRE_ENCAP``
2368 ^^^^^^^^^^^^^^^^^^^^^^^
2370 Performs a NVGRE encapsulation action by encapsulating the matched flow in the
2371 NVGRE tunnel as defined in the``rte_flow_action_tunnel_encap`` flow item
2374 This action modifies the payload of matched flows. The flow definition specified
2375 in the ``rte_flow_action_tunnel_encap`` action structure must defined a valid
2376 NVGRE network overlay which conforms with RFC 7637 (NVGRE: Network
2377 Virtualization Using Generic Routing Encapsulation). The pattern must be
2378 terminated with the RTE_FLOW_ITEM_TYPE_END item type.
2380 .. _table_rte_flow_action_nvgre_encap:
2382 .. table:: NVGRE_ENCAP
2384 +----------------+-------------------------------------+
2386 +================+=====================================+
2387 | ``definition`` | NVGRE end-point overlay definition |
2388 +----------------+-------------------------------------+
2390 .. _table_rte_flow_action_nvgre_encap_example:
2392 .. table:: IPv4 NVGRE flow pattern example.
2394 +-------+----------+
2396 +=======+==========+
2398 +-------+----------+
2400 +-------+----------+
2402 +-------+----------+
2404 +-------+----------+
2406 Action: ``NVGRE_DECAP``
2407 ^^^^^^^^^^^^^^^^^^^^^^^
2409 Performs a decapsulation action by stripping all headers of the NVGRE tunnel
2410 network overlay from the matched flow.
2412 The flow items pattern defined for the flow rule with which a ``NVGRE_DECAP``
2413 action is specified, must define a valid NVGRE tunnel as per RFC7637. If the
2414 flow pattern does not specify a valid NVGRE tunnel then a
2415 RTE_FLOW_ERROR_TYPE_ACTION error should be returned.
2417 This action modifies the payload of matched flows.
2419 Action: ``RAW_ENCAP``
2420 ^^^^^^^^^^^^^^^^^^^^^
2422 Adds outer header whose template is provided in its data buffer,
2423 as defined in the ``rte_flow_action_raw_encap`` definition.
2425 This action modifies the payload of matched flows. The data supplied must
2426 be a valid header, either holding layer 2 data in case of adding layer 2 after
2427 decap layer 3 tunnel (for example MPLSoGRE) or complete tunnel definition
2428 starting from layer 2 and moving to the tunnel item itself. When applied to
2429 the original packet the resulting packet must be a valid packet.
2431 .. _table_rte_flow_action_raw_encap:
2433 .. table:: RAW_ENCAP
2435 +----------------+----------------------------------------+
2437 +================+========================================+
2438 | ``data`` | Encapsulation data |
2439 +----------------+----------------------------------------+
2440 | ``preserve`` | Bit-mask of data to preserve on output |
2441 +----------------+----------------------------------------+
2442 | ``size`` | Size of data and preserve |
2443 +----------------+----------------------------------------+
2445 Action: ``RAW_DECAP``
2446 ^^^^^^^^^^^^^^^^^^^^^^^
2448 Remove outer header whose template is provided in its data buffer,
2449 as defined in the ``rte_flow_action_raw_decap``
2451 This action modifies the payload of matched flows. The data supplied must
2452 be a valid header, either holding layer 2 data in case of removing layer 2
2453 before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
2454 tunnel definition starting from layer 2 and moving to the tunnel item itself.
2455 When applied to the original packet the resulting packet must be a
2458 .. _table_rte_flow_action_raw_decap:
2460 .. table:: RAW_DECAP
2462 +----------------+----------------------------------------+
2464 +================+========================================+
2465 | ``data`` | Decapsulation data |
2466 +----------------+----------------------------------------+
2467 | ``size`` | Size of data |
2468 +----------------+----------------------------------------+
2470 Action: ``SET_IPV4_SRC``
2471 ^^^^^^^^^^^^^^^^^^^^^^^^
2473 Set a new IPv4 source address in the outermost IPv4 header.
2475 It must be used with a valid RTE_FLOW_ITEM_TYPE_IPV4 flow pattern item.
2476 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2478 .. _table_rte_flow_action_set_ipv4_src:
2480 .. table:: SET_IPV4_SRC
2482 +-----------------------------------------+
2484 +===============+=========================+
2485 | ``ipv4_addr`` | new IPv4 source address |
2486 +---------------+-------------------------+
2488 Action: ``SET_IPV4_DST``
2489 ^^^^^^^^^^^^^^^^^^^^^^^^
2491 Set a new IPv4 destination address in the outermost IPv4 header.
2493 It must be used with a valid RTE_FLOW_ITEM_TYPE_IPV4 flow pattern item.
2494 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2496 .. _table_rte_flow_action_set_ipv4_dst:
2498 .. table:: SET_IPV4_DST
2500 +---------------+------------------------------+
2502 +===============+==============================+
2503 | ``ipv4_addr`` | new IPv4 destination address |
2504 +---------------+------------------------------+
2506 Action: ``SET_IPV6_SRC``
2507 ^^^^^^^^^^^^^^^^^^^^^^^^
2509 Set a new IPv6 source address in the outermost IPv6 header.
2511 It must be used with a valid RTE_FLOW_ITEM_TYPE_IPV6 flow pattern item.
2512 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2514 .. _table_rte_flow_action_set_ipv6_src:
2516 .. table:: SET_IPV6_SRC
2518 +---------------+-------------------------+
2520 +===============+=========================+
2521 | ``ipv6_addr`` | new IPv6 source address |
2522 +---------------+-------------------------+
2524 Action: ``SET_IPV6_DST``
2525 ^^^^^^^^^^^^^^^^^^^^^^^^
2527 Set a new IPv6 destination address in the outermost IPv6 header.
2529 It must be used with a valid RTE_FLOW_ITEM_TYPE_IPV6 flow pattern item.
2530 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2532 .. _table_rte_flow_action_set_ipv6_dst:
2534 .. table:: SET_IPV6_DST
2536 +---------------+------------------------------+
2538 +===============+==============================+
2539 | ``ipv6_addr`` | new IPv6 destination address |
2540 +---------------+------------------------------+
2542 Action: ``SET_TP_SRC``
2543 ^^^^^^^^^^^^^^^^^^^^^^^^^
2545 Set a new source port number in the outermost TCP/UDP header.
2547 It must be used with a valid RTE_FLOW_ITEM_TYPE_TCP or RTE_FLOW_ITEM_TYPE_UDP
2548 flow pattern item. Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2550 .. _table_rte_flow_action_set_tp_src:
2552 .. table:: SET_TP_SRC
2554 +----------+-------------------------+
2556 +==========+=========================+
2557 | ``port`` | new TCP/UDP source port |
2558 +---------------+--------------------+
2560 Action: ``SET_TP_DST``
2561 ^^^^^^^^^^^^^^^^^^^^^^^^^
2563 Set a new destination port number in the outermost TCP/UDP header.
2565 It must be used with a valid RTE_FLOW_ITEM_TYPE_TCP or RTE_FLOW_ITEM_TYPE_UDP
2566 flow pattern item. Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2568 .. _table_rte_flow_action_set_tp_dst:
2570 .. table:: SET_TP_DST
2572 +----------+------------------------------+
2574 +==========+==============================+
2575 | ``port`` | new TCP/UDP destination port |
2576 +---------------+-------------------------+
2578 Action: ``MAC_SWAP``
2579 ^^^^^^^^^^^^^^^^^^^^^^^^^
2581 Swap the source and destination MAC addresses in the outermost Ethernet
2584 It must be used with a valid RTE_FLOW_ITEM_TYPE_ETH flow pattern item.
2585 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2587 .. _table_rte_flow_action_mac_swap:
2602 If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
2603 in pattern, Some PMDs will reject rule because behavior will be undefined.
2605 .. _table_rte_flow_action_dec_ttl:
2618 Assigns a new TTL value.
2620 If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
2621 in pattern, Some PMDs will reject rule because behavior will be undefined.
2623 .. _table_rte_flow_action_set_ttl:
2627 +---------------+--------------------+
2629 +===============+====================+
2630 | ``ttl_value`` | new TTL value |
2631 +---------------+--------------------+
2633 Action: ``SET_MAC_SRC``
2634 ^^^^^^^^^^^^^^^^^^^^^^^
2636 Set source MAC address.
2638 It must be used with a valid RTE_FLOW_ITEM_TYPE_ETH flow pattern item.
2639 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2641 .. _table_rte_flow_action_set_mac_src:
2643 .. table:: SET_MAC_SRC
2645 +--------------+---------------+
2647 +==============+===============+
2648 | ``mac_addr`` | MAC address |
2649 +--------------+---------------+
2651 Action: ``SET_MAC_DST``
2652 ^^^^^^^^^^^^^^^^^^^^^^^
2654 Set destination MAC address.
2656 It must be used with a valid RTE_FLOW_ITEM_TYPE_ETH flow pattern item.
2657 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2659 .. _table_rte_flow_action_set_mac_dst:
2661 .. table:: SET_MAC_DST
2663 +--------------+---------------+
2665 +==============+===============+
2666 | ``mac_addr`` | MAC address |
2667 +--------------+---------------+
2669 Action: ``INC_TCP_SEQ``
2670 ^^^^^^^^^^^^^^^^^^^^^^^
2672 Increase sequence number in the outermost TCP header.
2673 Value to increase TCP sequence number by is a big-endian 32 bit integer.
2675 Using this action on non-matching traffic will result in undefined behavior.
2677 Action: ``DEC_TCP_SEQ``
2678 ^^^^^^^^^^^^^^^^^^^^^^^
2680 Decrease sequence number in the outermost TCP header.
2681 Value to decrease TCP sequence number by is a big-endian 32 bit integer.
2683 Using this action on non-matching traffic will result in undefined behavior.
2685 Action: ``INC_TCP_ACK``
2686 ^^^^^^^^^^^^^^^^^^^^^^^
2688 Increase acknowledgment number in the outermost TCP header.
2689 Value to increase TCP acknowledgment number by is a big-endian 32 bit integer.
2691 Using this action on non-matching traffic will result in undefined behavior.
2693 Action: ``DEC_TCP_ACK``
2694 ^^^^^^^^^^^^^^^^^^^^^^^
2696 Decrease acknowledgment number in the outermost TCP header.
2697 Value to decrease TCP acknowledgment number by is a big-endian 32 bit integer.
2699 Using this action on non-matching traffic will result in undefined behavior.
2706 Tag is a transient data used during flow matching. This is not delivered to
2707 application. Multiple tags are supported by specifying index.
2709 .. _table_rte_flow_action_set_tag:
2713 +-----------+----------------------------+
2715 +===========+============================+
2716 | ``data`` | 32 bit tag value |
2717 +-----------+----------------------------+
2718 | ``mask`` | bit-mask applies to "data" |
2719 +-----------+----------------------------+
2720 | ``index`` | index of tag to set |
2721 +-----------+----------------------------+
2723 Action: ``SET_META``
2724 ^^^^^^^^^^^^^^^^^^^^^^^
2726 Set metadata. Item ``META`` matches metadata.
2728 Metadata set by mbuf metadata field with PKT_TX_DYNF_METADATA flag on egress
2729 will be overridden by this action. On ingress, the metadata will be carried by
2730 ``metadata`` dynamic field of ``rte_mbuf`` which can be accessed by
2731 ``RTE_FLOW_DYNF_METADATA()``. PKT_RX_DYNF_METADATA flag will be set along
2734 The mbuf dynamic field must be registered by calling
2735 ``rte_flow_dynf_metadata_register()`` prior to use ``SET_META`` action.
2737 Altering partial bits is supported with ``mask``. For bits which have never been
2738 set, unpredictable value will be seen depending on driver implementation. For
2739 loopback/hairpin packet, metadata set on Rx/Tx may or may not be propagated to
2740 the other path depending on HW capability.
2742 In hairpin case with Tx explicit flow mode, metadata could (not mandatory) be
2743 used to connect the Rx and Tx flows if it can be propagated from Rx to Tx path.
2745 .. _table_rte_flow_action_set_meta:
2749 +----------+----------------------------+
2751 +==========+============================+
2752 | ``data`` | 32 bit metadata value |
2753 +----------+----------------------------+
2754 | ``mask`` | bit-mask applies to "data" |
2755 +----------+----------------------------+
2757 Action: ``SET_IPV4_DSCP``
2758 ^^^^^^^^^^^^^^^^^^^^^^^^^
2762 Modify DSCP in IPv4 header.
2764 It must be used with RTE_FLOW_ITEM_TYPE_IPV4 in pattern.
2765 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2767 .. _table_rte_flow_action_set_ipv4_dscp:
2769 .. table:: SET_IPV4_DSCP
2771 +-----------+---------------------------------+
2773 +===========+=================================+
2774 | ``dscp`` | DSCP in low 6 bits, rest ignore |
2775 +-----------+---------------------------------+
2777 Action: ``SET_IPV6_DSCP``
2778 ^^^^^^^^^^^^^^^^^^^^^^^^^
2782 Modify DSCP in IPv6 header.
2784 It must be used with RTE_FLOW_ITEM_TYPE_IPV6 in pattern.
2785 Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error will be returned.
2787 .. _table_rte_flow_action_set_ipv6_dscp:
2789 .. table:: SET_IPV6_DSCP
2791 +-----------+---------------------------------+
2793 +===========+=================================+
2794 | ``dscp`` | DSCP in low 6 bits, rest ignore |
2795 +-----------+---------------------------------+
2800 Set ageing timeout configuration to a flow.
2802 Event RTE_ETH_EVENT_FLOW_AGED will be reported if
2803 timeout passed without any matching on the flow.
2805 .. _table_rte_flow_action_age:
2809 +--------------+---------------------------------+
2811 +==============+=================================+
2812 | ``timeout`` | 24 bits timeout value |
2813 +--------------+---------------------------------+
2814 | ``reserved`` | 8 bits reserved, must be zero |
2815 +--------------+---------------------------------+
2816 | ``context`` | user input flow context |
2817 +--------------+---------------------------------+
2819 Query structure to retrieve ageing status information of a
2820 shared AGE action, or a flow rule using the AGE action:
2822 .. _table_rte_flow_query_age:
2824 .. table:: AGE query
2826 +------------------------------+-----+----------------------------------------+
2827 | Field | I/O | Value |
2828 +==============================+=====+========================================+
2829 | ``aged`` | out | Aging timeout expired |
2830 +------------------------------+-----+----------------------------------------+
2831 | ``sec_since_last_hit_valid`` | out | ``sec_since_last_hit`` value is valid |
2832 +------------------------------+-----+----------------------------------------+
2833 | ``sec_since_last_hit`` | out | Seconds since last traffic hit |
2834 +------------------------------+-----+----------------------------------------+
2839 Adds a sample action to a matched flow.
2841 The matching packets will be duplicated with the specified ``ratio`` and
2842 applied with own set of actions with a fate action, the packets sampled
2843 equals is '1/ratio'. All the packets continue to the target destination.
2845 When the ``ratio`` is set to 1 then the packets will be 100% mirrored.
2846 ``actions`` represent the different set of actions for the sampled or mirrored
2847 packets, and must have a fate action.
2849 .. _table_rte_flow_action_sample:
2853 +--------------+---------------------------------+
2855 +==============+=================================+
2856 | ``ratio`` | 32 bits sample ratio value |
2857 +--------------+---------------------------------+
2858 | ``actions`` | sub-action list for sampling |
2859 +--------------+---------------------------------+
2861 Action: ``INDIRECT``
2862 ^^^^^^^^^^^^^^^^^^^^
2864 Flow utilize indirect action by handle as returned from
2865 ``rte_flow_action_handle_create()``.
2867 The behaviour of the indirect action defined by ``action`` argument of type
2868 ``struct rte_flow_action`` passed to ``rte_flow_action_handle_create()``.
2870 The indirect action can be used by a single flow or shared among multiple flows.
2871 The indirect action can be in-place updated by ``rte_flow_action_handle_update()``
2872 without destroying flow and creating flow again. The fields that could be
2873 updated depend on the type of the ``action`` and different for every type.
2875 The indirect action specified data (e.g. counter) can be queried by
2876 ``rte_flow_action_handle_query()``.
2878 .. _table_rte_flow_action_handle:
2888 Action: ``MODIFY_FIELD``
2889 ^^^^^^^^^^^^^^^^^^^^^^^^
2891 Modify ``dst`` field according to ``op`` selected (set, addition,
2892 subtraction) with ``width`` bits of data from ``src`` field.
2894 Any arbitrary header field (as well as mark, metadata or tag values)
2895 can be used as both source and destination fields as set by ``field``.
2896 The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
2897 ``RTE_FLOW_FIELD_POINTER``) is allowed as a source only.
2898 ``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
2899 See ``enum rte_flow_field_id`` for the list of supported fields.
2901 ``op`` selects the operation to perform on a destination field.
2902 - ``set`` copies the data from ``src`` field to ``dst`` field.
2903 - ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
2904 - ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
2906 ``width`` defines a number of bits to use from ``src`` field.
2908 ``level`` is used to access any packet field on any encapsulation level
2909 as well as any tag element in the tag array.
2910 - ``0`` means the default behaviour. Depending on the packet type, it can
2911 mean outermost, innermost or anything in between.
2912 - ``1`` requests access to the outermost packet encapsulation level.
2913 - ``2`` and subsequent values requests access to the specified packet
2914 encapsulation level, from outermost to innermost (lower to higher values).
2915 For the tag array (in case of multiple tags are supported and present)
2916 ``level`` translates directly into the array index.
2918 ``offset`` specifies the number of bits to skip from a field's start.
2919 That allows performing a partial copy of the needed part or to divide a big
2920 packet field into multiple smaller fields. Alternatively, ``offset`` allows
2921 going past the specified packet field boundary to copy a field to an
2922 arbitrary place in a packet, essentially providing a way to copy any part of
2923 a packet to any other part of it.
2925 ``value`` sets an immediate value to be used as a source or points to a
2926 location of the value in memory. It is used instead of ``level`` and ``offset``
2927 for ``RTE_FLOW_FIELD_VALUE`` and ``RTE_FLOW_FIELD_POINTER`` respectively.
2929 .. _table_rte_flow_action_modify_field:
2931 .. table:: MODIFY_FIELD
2933 +---------------+-------------------------+
2935 +===============+=========================+
2936 | ``op`` | operation to perform |
2937 +---------------+-------------------------+
2938 | ``dst`` | destination field |
2939 +---------------+-------------------------+
2940 | ``src`` | source field |
2941 +---------------+-------------------------+
2942 | ``width`` | number of bits to use |
2943 +---------------+-------------------------+
2945 .. _table_rte_flow_action_modify_data:
2947 .. table:: destination/source field definition
2949 +---------------+----------------------------------------------------------+
2951 +===============+==========================================================+
2952 | ``field`` | ID: packet field, mark, meta, tag, immediate, pointer |
2953 +---------------+----------------------------------------------------------+
2954 | ``level`` | encapsulation level of a packet field or tag array index |
2955 +---------------+----------------------------------------------------------+
2956 | ``offset`` | number of bits to skip at the beginning |
2957 +---------------+----------------------------------------------------------+
2958 | ``value`` | immediate value or a pointer to this value |
2959 +---------------+----------------------------------------------------------+
2961 Action: ``CONNTRACK``
2962 ^^^^^^^^^^^^^^^^^^^^^
2964 Create a conntrack (connection tracking) context with the provided information.
2966 In stateful session like TCP, the conntrack action provides the ability to
2967 examine every packet of this connection and associate the state to every
2968 packet. It will help to realize the stateful offload of connections with little
2969 software participation. For example, the packets with invalid state may be
2970 handled by the software. The control packets could be handled in the hardware.
2971 The software just need to query the state of a connection when needed, and then
2972 decide how to handle the flow rules and conntrack context.
2974 A conntrack context should be created via ``rte_flow_action_handle_create()``
2975 before using. Then the handle with ``INDIRECT`` type is used for a flow rule
2976 creation. If a flow rule with an opposite direction needs to be created, the
2977 ``rte_flow_action_handle_update()`` should be used to modify the direction.
2979 Not all the fields of the ``struct rte_flow_action_conntrack`` will be used
2980 for a conntrack context creating, depending on the HW, and they should be
2981 in host byte order. PMD should convert them into network byte order when
2984 The ``struct rte_flow_modify_conntrack`` should be used for an updating.
2986 The current conntrack context information could be queried via the
2987 ``rte_flow_action_handle_query()`` interface.
2989 .. _table_rte_flow_action_conntrack:
2991 .. table:: CONNTRACK
2993 +--------------------------+-------------------------------------------------------------+
2995 +==========================+=============================================================+
2996 | ``peer_port`` | peer port number |
2997 +--------------------------+-------------------------------------------------------------+
2998 | ``is_original_dir`` | direction of this connection for creating flow rule |
2999 +--------------------------+-------------------------------------------------------------+
3000 | ``enable`` | enable the conntrack context |
3001 +--------------------------+-------------------------------------------------------------+
3002 | ``live_connection`` | one ack was seen for this connection |
3003 +--------------------------+-------------------------------------------------------------+
3004 | ``selective_ack`` | SACK enabled |
3005 +--------------------------+-------------------------------------------------------------+
3006 | ``challenge_ack_passed`` | a challenge ack has passed |
3007 +--------------------------+-------------------------------------------------------------+
3008 | ``last_direction`` | direction of the last passed packet |
3009 +--------------------------+-------------------------------------------------------------+
3010 | ``liberal_mode`` | only report state change |
3011 +--------------------------+-------------------------------------------------------------+
3012 | ``state`` | current state |
3013 +--------------------------+-------------------------------------------------------------+
3014 | ``max_ack_window`` | maximal window scaling factor |
3015 +--------------------------+-------------------------------------------------------------+
3016 | ``retransmission_limit`` | maximal retransmission times |
3017 +--------------------------+-------------------------------------------------------------+
3018 | ``original_dir`` | TCP parameters of the original direction |
3019 +--------------------------+-------------------------------------------------------------+
3020 | ``reply_dir`` | TCP parameters of the reply direction |
3021 +--------------------------+-------------------------------------------------------------+
3022 | ``last_window`` | window size of the last passed packet |
3023 +--------------------------+-------------------------------------------------------------+
3024 | ``last_seq`` | sequence number of the last passed packet |
3025 +--------------------------+-------------------------------------------------------------+
3026 | ``last_ack`` | acknowledgment number the last passed packet |
3027 +--------------------------+-------------------------------------------------------------+
3028 | ``last_end`` | sum of ack number and length of the last passed packet |
3029 +--------------------------+-------------------------------------------------------------+
3031 .. _table_rte_flow_tcp_dir_param:
3033 .. table:: configuration parameters for each direction
3035 +---------------------+---------------------------------------------------------+
3037 +=====================+=========================================================+
3038 | ``scale`` | TCP window scaling factor |
3039 +---------------------+---------------------------------------------------------+
3040 | ``close_initiated`` | FIN sent from this direction |
3041 +---------------------+---------------------------------------------------------+
3042 | ``last_ack_seen`` | an ACK packet received |
3043 +---------------------+---------------------------------------------------------+
3044 | ``data_unacked`` | unacknowledged data for packets from this direction |
3045 +---------------------+---------------------------------------------------------+
3046 | ``sent_end`` | max{seq + len} seen in sent packets |
3047 +---------------------+---------------------------------------------------------+
3048 | ``reply_end`` | max{sack + max{win, 1}} seen in reply packets |
3049 +---------------------+---------------------------------------------------------+
3050 | ``max_win`` | max{max{win, 1}} + {sack - ack} seen in sent packets |
3051 +---------------------+---------------------------------------------------------+
3052 | ``max_ack`` | max{ack} + seen in sent packets |
3053 +---------------------+---------------------------------------------------------+
3055 .. _table_rte_flow_modify_conntrack:
3057 .. table:: update a conntrack context
3059 +----------------+-------------------------------------------------+
3061 +================+=================================================+
3062 | ``new_ct`` | new conntrack information |
3063 +----------------+-------------------------------------------------+
3064 | ``direction`` | direction will be updated |
3065 +----------------+-------------------------------------------------+
3066 | ``state`` | other fields except direction will be updated |
3067 +----------------+-------------------------------------------------+
3068 | ``reserved`` | reserved bits |
3069 +----------------+-------------------------------------------------+
3071 Action: ``METER_COLOR``
3072 ^^^^^^^^^^^^^^^^^^^^^^^
3074 Color the packet to reflect the meter color result.
3076 The meter action must be configured before meter color action.
3077 Meter color action is set to a color to reflect the meter color result.
3078 Set the meter color in the mbuf to the selected color.
3079 The meter color action output color is the output color of the packet,
3080 which is set in the packet meta-data (i.e. struct ``rte_mbuf::sched::color``)
3082 .. _table_rte_flow_action_meter_color:
3084 .. table:: METER_COLOR
3086 +-----------------+--------------+
3088 +=================+==============+
3089 | ``meter_color`` | Packet color |
3090 +-----------------+--------------+
3095 All specified pattern items (``enum rte_flow_item_type``) and actions
3096 (``enum rte_flow_action_type``) use positive identifiers.
3098 The negative space is reserved for dynamic types generated by PMDs during
3099 run-time. PMDs may encounter them as a result but must not accept negative
3100 identifiers they are not aware of.
3102 A method to generate them remains to be defined.
3104 Application may use PMD dynamic items or actions in flow rules. In that case
3105 size of configuration object in dynamic element must be a pointer size.
3110 A rather simple API with few functions is provided to fully manage flow
3113 Each created flow rule is associated with an opaque, PMD-specific handle
3114 pointer. The application is responsible for keeping it until the rule is
3117 Flows rules are represented by ``struct rte_flow`` objects.
3122 Given that expressing a definite set of device capabilities is not
3123 practical, a dedicated function is provided to check if a flow rule is
3124 supported and can be created.
3129 rte_flow_validate(uint16_t port_id,
3130 const struct rte_flow_attr *attr,
3131 const struct rte_flow_item pattern[],
3132 const struct rte_flow_action actions[],
3133 struct rte_flow_error *error);
3135 The flow rule is validated for correctness and whether it could be accepted
3136 by the device given sufficient resources. The rule is checked against the
3137 current device mode and queue configuration. The flow rule may also
3138 optionally be validated against existing flow rules and device resources.
3139 This function has no effect on the target device.
3141 The returned value is guaranteed to remain valid only as long as no
3142 successful calls to ``rte_flow_create()`` or ``rte_flow_destroy()`` are made
3143 in the meantime and no device parameter affecting flow rules in any way are
3144 modified, due to possible collisions or resource limitations (although in
3145 such cases ``EINVAL`` should not be returned).
3149 - ``port_id``: port identifier of Ethernet device.
3150 - ``attr``: flow rule attributes.
3151 - ``pattern``: pattern specification (list terminated by the END pattern
3153 - ``actions``: associated actions (list terminated by the END action).
3154 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3155 this structure in case of error only.
3159 - 0 if flow rule is valid and can be created. A negative errno value
3160 otherwise (``rte_errno`` is also set), the following errors are defined.
3161 - ``-ENOSYS``: underlying device does not support this functionality.
3162 - ``-EINVAL``: unknown or invalid rule specification.
3163 - ``-ENOTSUP``: valid but unsupported rule specification (e.g. partial
3164 bit-masks are unsupported).
3165 - ``EEXIST``: collision with an existing rule. Only returned if device
3166 supports flow rule collision checking and there was a flow rule
3167 collision. Not receiving this return code is no guarantee that creating
3168 the rule will not fail due to a collision.
3169 - ``ENOMEM``: not enough memory to execute the function, or if the device
3170 supports resource validation, resource limitation on the device.
3171 - ``-EBUSY``: action cannot be performed due to busy device resources, may
3172 succeed if the affected queues or even the entire port are in a stopped
3173 state (see ``rte_eth_dev_rx_queue_stop()`` and ``rte_eth_dev_stop()``).
3178 Creating a flow rule is similar to validating one, except the rule is
3179 actually created and a handle returned.
3184 rte_flow_create(uint16_t port_id,
3185 const struct rte_flow_attr *attr,
3186 const struct rte_flow_item pattern[],
3187 const struct rte_flow_action *actions[],
3188 struct rte_flow_error *error);
3192 - ``port_id``: port identifier of Ethernet device.
3193 - ``attr``: flow rule attributes.
3194 - ``pattern``: pattern specification (list terminated by the END pattern
3196 - ``actions``: associated actions (list terminated by the END action).
3197 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3198 this structure in case of error only.
3202 A valid handle in case of success, NULL otherwise and ``rte_errno`` is set
3203 to the positive version of one of the error codes defined for
3204 ``rte_flow_validate()``.
3209 Flow rules destruction is not automatic, and a queue or a port should not be
3210 released if any are still attached to them. Applications must take care of
3211 performing this step before releasing resources.
3216 rte_flow_destroy(uint16_t port_id,
3217 struct rte_flow *flow,
3218 struct rte_flow_error *error);
3221 Failure to destroy a flow rule handle may occur when other flow rules depend
3222 on it, and destroying it would result in an inconsistent state.
3224 This function is only guaranteed to succeed if handles are destroyed in
3225 reverse order of their creation.
3229 - ``port_id``: port identifier of Ethernet device.
3230 - ``flow``: flow rule handle to destroy.
3231 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3232 this structure in case of error only.
3236 - 0 on success, a negative errno value otherwise and ``rte_errno`` is set.
3241 Convenience function to destroy all flow rule handles associated with a
3242 port. They are released as with successive calls to ``rte_flow_destroy()``.
3247 rte_flow_flush(uint16_t port_id,
3248 struct rte_flow_error *error);
3250 In the unlikely event of failure, handles are still considered destroyed and
3251 no longer valid but the port must be assumed to be in an inconsistent state.
3255 - ``port_id``: port identifier of Ethernet device.
3256 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3257 this structure in case of error only.
3261 - 0 on success, a negative errno value otherwise and ``rte_errno`` is set.
3266 Query an existing flow rule.
3268 This function allows retrieving flow-specific data such as counters. Data
3269 is gathered by special actions which must be present in the flow rule
3275 rte_flow_query(uint16_t port_id,
3276 struct rte_flow *flow,
3277 const struct rte_flow_action *action,
3279 struct rte_flow_error *error);
3283 - ``port_id``: port identifier of Ethernet device.
3284 - ``flow``: flow rule handle to query.
3285 - ``action``: action to query, this must match prototype from flow rule.
3286 - ``data``: pointer to storage for the associated query data type.
3287 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3288 this structure in case of error only.
3292 - 0 on success, a negative errno value otherwise and ``rte_errno`` is set.
3294 .. _flow_isolated_mode:
3299 The general expectation for ingress traffic is that flow rules process it
3300 first; the remaining unmatched or pass-through traffic usually ends up in a
3301 queue (with or without RSS, locally or in some sub-device instance)
3302 depending on the global configuration settings of a port.
3304 While fine from a compatibility standpoint, this approach makes drivers more
3305 complex as they have to check for possible side effects outside of this API
3306 when creating or destroying flow rules. It results in a more limited set of
3307 available rule types due to the way device resources are assigned (e.g. no
3308 support for the RSS action even on capable hardware).
3310 Given that nonspecific traffic can be handled by flow rules as well,
3311 isolated mode is a means for applications to tell a driver that ingress on
3312 the underlying port must be injected from the defined flow rules only; that
3313 no default traffic is expected outside those rules.
3315 This has the following benefits:
3317 - Applications get finer-grained control over the kind of traffic they want
3318 to receive (no traffic by default).
3320 - More importantly they control at what point nonspecific traffic is handled
3321 relative to other flow rules, by adjusting priority levels.
3323 - Drivers can assign more hardware resources to flow rules and expand the
3324 set of supported rule types.
3326 Because toggling isolated mode may cause profound changes to the ingress
3327 processing path of a driver, it may not be possible to leave it once
3328 entered. Likewise, existing flow rules or global configuration settings may
3329 prevent a driver from entering isolated mode.
3331 Applications relying on this mode are therefore encouraged to toggle it as
3332 soon as possible after device initialization, ideally before the first call
3333 to ``rte_eth_dev_configure()`` to avoid possible failures due to conflicting
3336 Once effective, the following functionality has no effect on the underlying
3337 port and may return errors such as ``ENOTSUP`` ("not supported"):
3339 - Toggling promiscuous mode.
3340 - Toggling allmulticast mode.
3341 - Configuring MAC addresses.
3342 - Configuring multicast addresses.
3343 - Configuring VLAN filters.
3344 - Configuring global RSS settings.
3349 rte_flow_isolate(uint16_t port_id, int set, struct rte_flow_error *error);
3353 - ``port_id``: port identifier of Ethernet device.
3354 - ``set``: nonzero to enter isolated mode, attempt to leave it otherwise.
3355 - ``error``: perform verbose error reporting if not NULL. PMDs initialize
3356 this structure in case of error only.
3360 - 0 on success, a negative errno value otherwise and ``rte_errno`` is set.
3362 Verbose error reporting
3363 -----------------------
3365 The defined *errno* values may not be accurate enough for users or
3366 application developers who want to investigate issues related to flow rules
3367 management. A dedicated error object is defined for this purpose:
3371 enum rte_flow_error_type {
3372 RTE_FLOW_ERROR_TYPE_NONE, /**< No error. */
3373 RTE_FLOW_ERROR_TYPE_UNSPECIFIED, /**< Cause unspecified. */
3374 RTE_FLOW_ERROR_TYPE_HANDLE, /**< Flow rule (handle). */
3375 RTE_FLOW_ERROR_TYPE_ATTR_GROUP, /**< Group field. */
3376 RTE_FLOW_ERROR_TYPE_ATTR_PRIORITY, /**< Priority field. */
3377 RTE_FLOW_ERROR_TYPE_ATTR_INGRESS, /**< Ingress field. */
3378 RTE_FLOW_ERROR_TYPE_ATTR_EGRESS, /**< Egress field. */
3379 RTE_FLOW_ERROR_TYPE_ATTR, /**< Attributes structure. */
3380 RTE_FLOW_ERROR_TYPE_ITEM_NUM, /**< Pattern length. */
3381 RTE_FLOW_ERROR_TYPE_ITEM, /**< Specific pattern item. */
3382 RTE_FLOW_ERROR_TYPE_ACTION_NUM, /**< Number of actions. */
3383 RTE_FLOW_ERROR_TYPE_ACTION, /**< Specific action. */
3386 struct rte_flow_error {
3387 enum rte_flow_error_type type; /**< Cause field and error types. */
3388 const void *cause; /**< Object responsible for the error. */
3389 const char *message; /**< Human-readable error message. */
3392 Error type ``RTE_FLOW_ERROR_TYPE_NONE`` stands for no error, in which case
3393 remaining fields can be ignored. Other error types describe the type of the
3394 object pointed by ``cause``.
3396 If non-NULL, ``cause`` points to the object responsible for the error. For a
3397 flow rule, this may be a pattern item or an individual action.
3399 If non-NULL, ``message`` provides a human-readable error message.
3401 This object is normally allocated by applications and set by PMDs in case of
3402 error, the message points to a constant string which does not need to be
3403 freed by the application, however its pointer can be considered valid only
3404 as long as its associated DPDK port remains configured. Closing the
3405 underlying device or unloading the PMD invalidates it.
3416 rte_flow_error_set(struct rte_flow_error *error,
3418 enum rte_flow_error_type type,
3420 const char *message);
3422 This function initializes ``error`` (if non-NULL) with the provided
3423 parameters and sets ``rte_errno`` to ``code``. A negative error ``code`` is
3432 rte_flow_conv(enum rte_flow_conv_op op,
3436 struct rte_flow_error *error);
3438 Convert ``src`` to ``dst`` according to operation ``op``. Possible
3441 - Attributes, pattern item or action duplication.
3442 - Duplication of an entire pattern or list of actions.
3443 - Duplication of a complete flow rule description.
3444 - Pattern item or action name retrieval.
3446 Tunneled traffic offload
3447 ~~~~~~~~~~~~~~~~~~~~~~~~
3449 rte_flow API provides the building blocks for vendor-agnostic flow
3450 classification offloads. The rte_flow "patterns" and "actions"
3451 primitives are fine-grained, thus enabling DPDK applications the
3452 flexibility to offload network stacks and complex pipelines.
3453 Applications wishing to offload tunneled traffic are required to use
3454 the rte_flow primitives, such as group, meta, mark, tag, and others to
3455 model their high-level objects. The hardware model design for
3456 high-level software objects is not trivial. Furthermore, an optimal
3457 design is often vendor-specific.
3459 When hardware offloads tunneled traffic in multi-group logic,
3460 partially offloaded packets may arrive to the application after they
3461 were modified in hardware. In this case, the application may need to
3462 restore the original packet headers. Consider the following sequence:
3463 The application decaps a packet in one group and jumps to a second
3464 group where it tries to match on a 5-tuple, that will miss and send
3465 the packet to the application. In this case, the application does not
3466 receive the original packet but a modified one. Also, in this case,
3467 the application cannot match on the outer header fields, such as VXLAN
3470 There are several possible ways to use rte_flow "patterns" and
3471 "actions" to resolve the issues above. For example:
3473 1 Mapping headers to a hardware registers using the
3474 rte_flow_action_mark/rte_flow_action_tag/rte_flow_set_meta objects.
3476 2 Apply the decap only at the last offload stage after all the
3477 "patterns" were matched and the packet will be fully offloaded.
3479 Every approach has its pros and cons and is highly dependent on the
3480 hardware vendor. For example, some hardware may have a limited number
3481 of registers while other hardware could not support inner actions and
3482 must decap before accessing inner headers.
3484 The tunnel offload model resolves these issues. The model goals are:
3486 1 Provide a unified application API to offload tunneled traffic that
3487 is capable to match on outer headers after decap.
3489 2 Allow the application to restore the outer header of partially
3492 The tunnel offload model does not introduce new elements to the
3493 existing RTE flow model and is implemented as a set of helper
3496 For the application to work with the tunnel offload API it
3497 has to adjust flow rules in multi-table tunnel offload in the
3500 1 Remove explicit call to decap action and replace it with PMD actions
3501 obtained from rte_flow_tunnel_decap_and_set() helper.
3503 2 Add PMD items obtained from rte_flow_tunnel_match() helper to all
3504 other rules in the tunnel offload sequence.
3506 The model requirements:
3508 Software application must initialize
3509 rte_tunnel object with tunnel parameters before calling
3510 rte_flow_tunnel_decap_set() & rte_flow_tunnel_match().
3512 PMD actions array obtained in rte_flow_tunnel_decap_set() must be
3513 released by application with rte_flow_action_release() call.
3515 PMD items array obtained with rte_flow_tunnel_match() must be released
3516 by application with rte_flow_item_release() call. Application can
3517 release PMD items and actions after rule was created. However, if the
3518 application needs to create additional rule for the same tunnel it
3519 will need to obtain PMD items again.
3521 Application cannot destroy rte_tunnel object before it releases all
3522 PMD actions & PMD items referencing that tunnel.
3527 - DPDK does not keep track of flow rules definitions or flow rule objects
3528 automatically. Applications may keep track of the former and must keep
3529 track of the latter. PMDs may also do it for internal needs, however this
3530 must not be relied on by applications.
3532 - Flow rules are not maintained between successive port initializations. An
3533 application exiting without releasing them and restarting must re-create
3536 - API operations are synchronous and blocking (``EAGAIN`` cannot be
3539 - Stopping the data path (TX/RX) should not be necessary when managing flow
3540 rules. If this cannot be achieved naturally or with workarounds (such as
3541 temporarily replacing the burst function pointers), an appropriate error
3542 code must be returned (``EBUSY``).
3544 - Applications, not PMDs, are responsible for maintaining flow rules
3545 configuration when closing, stopping or restarting a port or performing other
3546 actions which may affect them.
3547 Applications must assume that after port close, stop or restart all flows
3548 related to that port are not valid, hardware rules are destroyed and relevant
3549 PMD resources are released.
3551 For devices exposing multiple ports sharing global settings affected by flow
3554 - All ports under DPDK control must behave consistently, PMDs are
3555 responsible for making sure that existing flow rules on a port are not
3556 affected by other ports.
3558 - Ports not under DPDK control (unaffected or handled by other applications)
3559 are user's responsibility. They may affect existing flow rules and cause
3560 undefined behavior. PMDs aware of this may prevent flow rules creation
3561 altogether in such cases.
3566 The PMD interface is defined in ``rte_flow_driver.h``. It is not subject to
3567 API/ABI versioning constraints as it is not exposed to applications and may
3568 evolve independently.
3570 The PMD interface is based on callbacks pointed by the ``struct rte_flow_ops``.
3572 - PMD callbacks implement exactly the interface described in `Rules
3573 management`_, except for the port ID argument which has already been
3574 converted to a pointer to the underlying ``struct rte_eth_dev``.
3576 - Public API functions do not process flow rules definitions at all before
3577 calling PMD functions (no basic error checking, no validation
3578 whatsoever). They only make sure these callbacks are non-NULL or return
3579 the ``ENOSYS`` (function not supported) error.
3581 This interface additionally defines the following helper function:
3583 - ``rte_flow_ops_get()``: get generic flow operations structure from a
3586 If PMD interfaces don't support re-entrancy/multi-thread safety,
3587 the rte_flow API functions will protect threads by mutex per port.
3588 The application can check whether ``RTE_ETH_DEV_FLOW_OPS_THREAD_SAFE``
3589 is set in ``dev_flags``, meaning the PMD is thread-safe regarding rte_flow,
3590 so the API level protection is disabled.
3591 Please note that this API-level mutex protects only rte_flow functions,
3592 other control path functions are not in scope.
3594 Device compatibility
3595 --------------------
3597 No known implementation supports all the described features.
3599 Unsupported features or combinations are not expected to be fully emulated
3600 in software by PMDs for performance reasons. Partially supported features
3601 may be completed in software as long as hardware performs most of the work
3602 (such as queue redirection and packet recognition).
3604 However PMDs are expected to do their best to satisfy application requests
3605 by working around hardware limitations as long as doing so does not affect
3606 the behavior of existing flow rules.
3608 The following sections provide a few examples of such cases and describe how
3609 PMDs should handle them, they are based on limitations built into the
3615 Each flow rule comes with its own, per-layer bit-masks, while hardware may
3616 support only a single, device-wide bit-mask for a given layer type, so that
3617 two IPv4 rules cannot use different bit-masks.
3619 The expected behavior in this case is that PMDs automatically configure
3620 global bit-masks according to the needs of the first flow rule created.
3622 Subsequent rules are allowed only if their bit-masks match those, the
3623 ``EEXIST`` error code should be returned otherwise.
3625 Unsupported layer types
3626 ~~~~~~~~~~~~~~~~~~~~~~~
3628 Many protocols can be simulated by crafting patterns with the `Item: RAW`_
3631 PMDs can rely on this capability to simulate support for protocols with
3632 headers not directly recognized by hardware.
3634 ``ANY`` pattern item
3635 ~~~~~~~~~~~~~~~~~~~~
3637 This pattern item stands for anything, which can be difficult to translate
3638 to something hardware would understand, particularly if followed by more
3641 Consider the following pattern:
3643 .. _table_rte_flow_unsupported_any:
3645 .. table:: Pattern with ANY as L3
3647 +-------+-----------------------+
3649 +=======+=======================+
3651 +-------+-----+---------+-------+
3652 | 1 | ANY | ``num`` | ``1`` |
3653 +-------+-----+---------+-------+
3655 +-------+-----------------------+
3657 +-------+-----------------------+
3659 Knowing that TCP does not make sense with something other than IPv4 and IPv6
3660 as L3, such a pattern may be translated to two flow rules instead:
3662 .. _table_rte_flow_unsupported_any_ipv4:
3664 .. table:: ANY replaced with IPV4
3666 +-------+--------------------+
3668 +=======+====================+
3670 +-------+--------------------+
3671 | 1 | IPV4 (zeroed mask) |
3672 +-------+--------------------+
3674 +-------+--------------------+
3676 +-------+--------------------+
3680 .. _table_rte_flow_unsupported_any_ipv6:
3682 .. table:: ANY replaced with IPV6
3684 +-------+--------------------+
3686 +=======+====================+
3688 +-------+--------------------+
3689 | 1 | IPV6 (zeroed mask) |
3690 +-------+--------------------+
3692 +-------+--------------------+
3694 +-------+--------------------+
3696 Note that as soon as a ANY rule covers several layers, this approach may
3697 yield a large number of hidden flow rules. It is thus suggested to only
3698 support the most common scenarios (anything as L2 and/or L3).
3703 - When combined with `Action: QUEUE`_, packet counting (`Action: COUNT`_)
3704 and tagging (`Action: MARK`_ or `Action: FLAG`_) may be implemented in
3705 software as long as the target queue is used by a single rule.
3707 - When a single target queue is provided, `Action: RSS`_ can also be
3708 implemented through `Action: QUEUE`_.
3713 While it would naturally make sense, flow rules cannot be assumed to be
3714 processed by hardware in the same order as their creation for several
3717 - They may be managed internally as a tree or a hash table instead of a
3719 - Removing a flow rule before adding another one can either put the new rule
3720 at the end of the list or reuse a freed entry.
3721 - Duplication may occur when packets are matched by several rules.
3723 For overlapping rules (particularly in order to use `Action: PASSTHRU`_)
3724 predictable behavior is only guaranteed by using different priority levels.
3726 Priority levels are not necessarily implemented in hardware, or may be
3727 severely limited (e.g. a single priority bit).
3729 For these reasons, priority levels may be implemented purely in software by
3732 - For devices expecting flow rules to be added in the correct order, PMDs
3733 may destroy and re-create existing rules after adding a new one with
3736 - A configurable number of dummy or empty rules can be created at
3737 initialization time to save high priority slots for later.
3739 - In order to save priority levels, PMDs may evaluate whether rules are
3740 likely to collide and adjust their priority accordingly.
3743 .. _OpenFlow Switch Specification: https://www.opennetworking.org/software-defined-standards/specifications/