efc1b2799f
The original design is to use rte_mbuf::udata64 to save the metadata of protocol extraction which has network protocol data fields and type, a private API is used to decode this metadata. Use the dynamic mbuf field and flags to register the needed fields in mbuf, to avoid overwriting 'rte_mbuf::udata64', since the application may use it. Now the protocol extraction metadate is saved into dynamic mbuf field with 4B size, and its type and validity is indicated by the related dynamic mbuf flags in 'rte_mbuf::ol_flags'. Signed-off-by: Haiyue Wang <haiyue.wang@intel.com> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
17 lines
336 B
Plaintext
17 lines
336 B
Plaintext
DPDK_19.02 {
|
|
|
|
local: *;
|
|
};
|
|
|
|
EXPERIMENTAL {
|
|
global:
|
|
|
|
# added in 19.11
|
|
rte_net_ice_dynfield_proto_xtr_metadata_offs;
|
|
rte_net_ice_dynflag_proto_xtr_vlan_mask;
|
|
rte_net_ice_dynflag_proto_xtr_ipv4_mask;
|
|
rte_net_ice_dynflag_proto_xtr_ipv6_mask;
|
|
rte_net_ice_dynflag_proto_xtr_ipv6_flow_mask;
|
|
rte_net_ice_dynflag_proto_xtr_tcp_mask;
|
|
};
|