23/05/2019 15:58, David Marchand:
> From: Stephen Hemminger <step...@networkplumber.org>
>
> The fields of the internal EAL core configuration are currently
> laid bare as part of the API. This is not good practice and limits
> fixing issues with layout and sizes.
>
> Make new accessor functions for the fields used by current drivers
> and examples.
[...]
> +DPDK_19.08 {
> + global:
> +
> + rte_lcore_cpuset;
> + rte_lcore_index;
> + rte_lcore_to_cpu_id;
> + rte_lcore_to_socket_id;
> +
> +} DPDK_19.05;
> +
> EXPERIMENTAL {
> global:
Just to make sure, are we OK to introduce these functions
as non-experimental?
