numam-dpdk/lib/librte_ring/rte_ring_version.map

DPDK_2.0 {
	global:

	rte_ring_create;
	rte_ring_dump;
	rte_ring_get_memsize;
	rte_ring_init;
	rte_ring_list_dump;
	rte_ring_lookup;

	local: *;
};

DPDK_2.2 {
	global:

	rte_ring_free;

} DPDK_2.0;

EXPERIMENTAL {
	global:

	rte_ring_reset;

};
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> 2015-02-02 17:40:20 +00:00			`DPDK_2.0 {`
			`global:`

			`rte_ring_create;`
			`rte_ring_dump;`
			`rte_ring_get_memsize;`
			`rte_ring_init;`
			`rte_ring_list_dump;`
			`rte_ring_lookup;`

			`local: *;`
			`};`
ring: support freeing When creating a ring, a memzone is created to allocate it in memory, but the ring could not be freed, as memzones could not be. Since memzones can be freed now, then rings can be as well, taking into account if they were initialized using pre-allocated memory (in which case, memory should be freed externally) or using rte_memzone_reserve (with rte_ring_create), freeing the memory with rte_memzone_free. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com> 2015-10-02 15:53:44 +00:00
			`DPDK_2.2 {`
			`global:`

			`rte_ring_free;`

			`} DPDK_2.0;`
ring: add reset function for flushing Currently, the flush is done by dequeuing the ring in a while loop. It is much simpler to flush the queue by resetting the head and tail indices. Signed-off-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Olivier Matz <olivier.matz@6wind.com> 2019-07-16 19:23:55 +00:00
			`EXPERIMENTAL {`
			`global:`

			`rte_ring_reset;`

			`};`