On Mon, Mar 14, 2016 at 03:42:45PM +0800, Jianfeng Tan wrote: > To achieve this, a new function pointer, dev_supported_ptypes_get, is added > into struct eth_dev_ops. For those devices who do not implement it, it > means it does not support any ptypes. > > v8: > - Rebased on dpdk-next-net/rel_16_04 branch. > - Rename ptypes_info -> supported_ptypes. > - Abandon info about newly added API in release_16_04.rst. > - concise -> correct. > > v7: > - 2.2 -> 16.04 > - Add note: this API better invoked after device is already started. > - Update release_16_04.rst for newly added API. > > v6: > - Remove extern in function declaration. > - Update rte_ether_version.map. > > v5: > - Exclude l3fwd change from this series, as a separated one. > - Fix malposition of mlx4 code in mlx5 commit introduced in v4. > > v4: > - Change how to use this API: to previously agreement reached in mail. > > v3: > - Change how to use this API: api to allocate mem for storing ptype > array; and caller to free the mem. > - Change how to return back ptypes from PMDs: return a pointer to > corresponding static const array of supported ptypes, terminated > by RTE_PTYPE_UNKNOWN. > - Fix l3fwd parse_packet_type() when EXACT_MATCH is enabled. > - Fix l3fwd memory leak when calling the API. > > v2: > - Move ptype_mask filter function from each PMDs into ether layer. > - Add ixgbe vPMD's ptype info. > - Fix code style issues. > > 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> > Applied to dpdk-next-net/rel_16_04, using v9 of patch 1 and v8 of all others.
/Bruce
