Hi Thomas,
On 3/15/2016 4:50 AM, Jianfeng Tan wrote:
> Add a new API rte_eth_dev_get_supported_ptypes to query what packet types
> can be filled by given already started device (or its pmd rx burst function
> has already been decided).
>
> Signed-off-by: Jianfeng Tan <jianfeng.tan at intel.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev at intel.com>
> Acked-by: Adrien Mazarguil <adrien.mazarguil at 6wind.com>
> ---
> v9:
> - Fix rte_ether_version.map as Ferruh Yigit sugguests.
> lib/librte_ether/rte_ethdev.c | 27 +++++++++++++++++++++++++++
> lib/librte_ether/rte_ethdev.h | 27 +++++++++++++++++++++++++++
> lib/librte_ether/rte_ether_version.map | 7 +++++++
> 3 files changed, 61 insertions(+)
...
> diff --git a/lib/librte_ether/rte_ether_version.map
> b/lib/librte_ether/rte_ether_version.map
> index d8db24d..c242e71 100644
> --- a/lib/librte_ether/rte_ether_version.map
> +++ b/lib/librte_ether/rte_ether_version.map
> @@ -117,3 +117,10 @@ DPDK_2.2 {
>
> local: *;
> };
> +
> +DPDK_16.04 {
> + global:
> +
> + rte_eth_dev_get_supported_ptypes;
> +
> +} DPDK_2.2;
Although this series is rebased on dpdk-next-net/rel_16_04, but applying
this into v16.04-rc1 only needs to remove change in
rte_ether_version.map. Shall I send a new version? Or this series will
simply be deferred?
Thanks,
Jianfeng
