| /dpdk/drivers/net/ipn3ke/ |
| H A D | ipn3ke_flow.c | 132 patterns, in ipn3ke_pattern_vxlan() 190 patterns, in ipn3ke_pattern_mac() 260 patterns, in ipn3ke_pattern_qinq() 334 patterns, in ipn3ke_pattern_mpls() 399 patterns, in ipn3ke_pattern_ip_tcp() 464 patterns, in ipn3ke_pattern_ip_udp() 538 patterns, in ipn3ke_pattern_ip_nvgre() 612 patterns, in ipn3ke_pattern_vxlan_ip_udp() 803 while ((*patterns == item->type) && in ipn3ke_match_pattern() 804 (*patterns != RTE_FLOW_ITEM_TYPE_END)) { in ipn3ke_match_pattern() [all …]
|
| /dpdk/drivers/net/failsafe/ |
| H A D | failsafe_flow.c | 67 const struct rte_flow_item patterns[], in fs_flow_validate() argument 79 attr, patterns, actions, error); in fs_flow_validate() 94 const struct rte_flow_item patterns[], in fs_flow_create() argument 103 flow = fs_flow_allocate(attr, patterns, actions); in fs_flow_create() 106 attr, patterns, actions, error); in fs_flow_create()
|
| /dpdk/drivers/net/bonding/ |
| H A D | rte_eth_bond_flow.c | 64 const struct rte_flow_item patterns[], in bond_flow_validate() argument 74 patterns, actions, err); in bond_flow_validate() 86 const struct rte_flow_item patterns[], in bond_flow_create() argument 94 flow = bond_flow_alloc(dev->data->numa_node, attr, patterns, actions); in bond_flow_create() 102 attr, patterns, actions, err); in bond_flow_create()
|
| /dpdk/drivers/net/i40e/base/ |
| H A D | i40e_diag.c | 35 const u32 patterns[] = {0x5A5A5A5A, 0xA5A5A5A5, 0x00000000, 0xFFFFFFFF}; in i40e_diag_reg_pattern_test() local 40 for (i = 0; i < ARRAY_SIZE(patterns); i++) { in i40e_diag_reg_pattern_test() 41 pat = patterns[i]; in i40e_diag_reg_pattern_test()
|
| /dpdk/drivers/net/igc/ |
| H A D | igc_flow.c | 158 igc_parse_patterns(const struct rte_flow_item patterns[], in igc_parse_patterns() argument 161 const struct rte_flow_item *item = patterns; in igc_parse_patterns() 267 const struct rte_flow_item patterns[], in igc_parse_flow() argument 284 ret = igc_parse_patterns(patterns, filter, error); in igc_parse_flow() 717 const struct rte_flow_item patterns[], in igc_flow_create() argument 725 ret = igc_parse_flow(dev, attr, patterns, actions, error, &filter); in igc_flow_create() 798 const struct rte_flow_item patterns[], in igc_flow_validate() argument 805 ret = igc_parse_flow(dev, attr, patterns, actions, error, &filter); in igc_flow_validate()
|
| /dpdk/ |
| H A D | .gitignore | 42 # ignore other build directory patterns
|
| H A D | MAINTAINERS | 13 F: Files and directories with wildcard patterns.
|
| /dpdk/drivers/net/qede/ |
| H A D | qede_filter.c | 936 const struct rte_flow_item patterns[], in qede_flow_parse() argument 952 rc = qede_flow_parse_pattern(dev, patterns, error, flow); in qede_flow_parse() 964 const struct rte_flow_item patterns[], in qede_flow_validate() argument 968 return qede_flow_parse(dev, attr, patterns, actions, error, NULL); in qede_flow_validate()
|
| /dpdk/doc/guides/nics/ |
| H A D | txgbe.rst | 160 different patterns and actions. Like ethertype filter defines a rule in pattern:
|
| H A D | qede.rst | 153 QLogic FastLinQ QL4xxxx NICs has support for the following patterns and
|
| H A D | cnxk.rst | 434 be the first item in the patterns specification.
|
| H A D | sfc_efx.rst | 286 There is a list of exceptional flow rule patterns which will not be
|
| H A D | mlx5.rst | 564 performance for different traffic patterns. Default format depends on
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_20_02.rst | 27 Added support for new flow item to handle L2TPv3 over IP rte_flow patterns. 119 Added support for ESP and L2TPv3 over IP rte_flow patterns to the testpmd
|
| H A D | release_22_03.rst | 36 with the same flow attributes and common matching patterns and actions
|
| H A D | release_20_05.rst | 138 * Added support for flow patterns with wildcard VLAN items (without VID value).
|
| H A D | release_21_11.rst | 95 with desired patterns and masks.
|
| /dpdk/drivers/bus/pci/bsd/ |
| H A D | pci.c | 336 .patterns = NULL, in rte_pci_scan()
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | switch_representation.rst | 369 **rte_flow** [6]_, which expresses flow rules as combinations of patterns 409 direction for matching patterns, but have no impact on actions. 539 neither the "transfer" attribute nor traffic origin in flow rule patterns
|
| H A D | flow_classify_lib.rst | 276 The library currently supports three IPv4 5-tuple flow patterns, for UDP, TCP
|
| H A D | rte_flow.rst | 185 Unless `Attribute: Transfer`_ is specified, flow rule patterns apply 1140 value, but it is possible two different patterns have the same hash value. 1679 Like matching patterns, action lists are terminated by END items. 4110 classification offloads. The rte_flow "patterns" and "actions" 4130 There are several possible ways to use rte_flow "patterns" and 4137 "patterns" were matched and the packet will be fully offloaded. 4288 Many protocols can be simulated by crafting patterns with the `Item: RAW`_
|
| H A D | graph_lib.rst | 175 the required nodes. The application can provide a set of node patterns to
|
| H A D | packet_framework.rst | 198 …| | | Table is a database of patterns, with each pattern having a pri… 201 …| | | The table lookup operation selects the patterns that is matched… 1176 frequently used patterns into vector-like instructions transparently to the user.
|
| H A D | env_abstraction_layer.rst | 187 very dependent on the memory allocation patterns of the application.
|