numam-dpdk/drivers/net/ice/version.map

DPDK_22 {
	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;
	rte_net_ice_dynflag_proto_xtr_ip_offset_mask;
};
version: 21.11-rc0 Start a new release cycle with empty release notes. The ABI version becomes 22.0. The map files are updated to the new ABI major number (22). The ABI exceptions are dropped and CI ABI checks are disabled because compatibility is not preserved. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: David Marchand <david.marchand@redhat.com> 2021-08-08 19:26:58 +00:00			`DPDK_22 {`
net/ice: support device initialization Update the documents too. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Signed-off-by: Qiming Yang <qiming.yang@intel.com> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com> 2018-12-18 08:46:24 +00:00			`local: *;`
			`};`
net/ice: optimize protocol extraction by dynamic mbuf 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> 2019-11-08 15:44:34 +00:00
			`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;`
net/ice: support auxiliary IP offset Rx descriptor Add RXDID #25 to support Auxiliary IP Offset Rx descriptor, including FlexiMD.4: Outer/Single IPv4 Header offset FlexiMD.5: Outer/Single IPv6 Header offset And parse the valid IP Offset into mbuf by flexible descriptor section via devargs "proto_xtr" with "proto_xtr=ip_offset". Signed-off-by: Junfeng Guo <junfeng.guo@intel.com> Acked-by: Haiyue Wang <haiyue.wang@intel.com> 2020-08-26 03:21:41 +00:00			`rte_net_ice_dynflag_proto_xtr_ip_offset_mask;`
net/ice: optimize protocol extraction by dynamic mbuf 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> 2019-11-08 15:44:34 +00:00			`};`