Pre-auxiliary Table Specifications

Name

None

Flow table name, which must comply with the DSL naming requirements.

Quantity

0 to 4

The total number of pre-auxiliary tables and post-auxiliary tables must be less than or equal to 4. Among them, both exact and fuzzy auxiliary tables are limited to a maximum of 2 each. This specification is used as a constraint. The programming framework does not enforce mandatory validation. A configuration that exceeds this specification is subject to the results of resource resolution.

Type

Pre-auxiliary table

Supports user declaration and stage-based division.

Keys

• rte_eth_hdr_t
• rte_vlan_hdr_t
• rte_ipv4_hdr_t
• rte_ipv6_hdr_t
• rte_tcp_hdr_t
• rte_udp_hdr_t
• rte_icmp_hdr_t
• rte_icmp6_hdr_t
• rte_vxlan_hdr_t
• rte_port_id_hdr_t
• rte_geneve_hdr_t
• Custom headers

Different tables support different keys, including DPDK standard headers and custom headers. The structures supported by the DPDK standard are defined in built-in header files that are not user-modifiable.

Actions

• flexda_ct
• rte_count
• flexda_upcall

These actions are often used for traffic distribution.

Matching mode

Exact and fuzzy

Classification by matching mode.

Number of entries (size)

512 (recommended)

The programming framework does not enforce mandatory validation. A configuration that exceeds the recommended value is subject to the results of resource resolution.

Key size

Exact auxiliary table: 16 bytes

Fuzzy auxiliary table: 80 bytes

If a key does not reach the upper limit, it will be padded to the upper limit.

Aging time

0

The aging function is not supported.