On Fri, Oct 25, 2019 at 6:56 PM Thomas Monjalon <tho...@monjalon.net> wrote: > > 25/10/2019 14:51, Ferruh Yigit: > > "Flow API" is a method/API to implement various filtering features, on > > its own it doesn't give much context on what features are provided. And > > it is not really a feature, so doesn't fit into feature table. > > > > Also since other filtering related APIs, 'filter_ctrl', has been > > deprecated, flow API is the only supported way in the DPDK to implement > > filtering options, if related filter options announced by PMDs, listing > > "Flow API" as implemented is redundant information. > > I fully agree with this explanation. > rte_flow is the only supported API for flow offloads. > That's why we must remove the legacy API. > > > Signed-off-by: Ferruh Yigit <ferruh.yi...@intel.com> > > --- > > --- a/doc/guides/nics/features/default.ini > > +++ b/doc/guides/nics/features/default.ini > > -Flow API = > > Acked-by: Thomas Monjalon <tho...@monjalon.net>
# Need to remove "Flow API" from doc/guides/nics/features.rst # Need to remove refference of "Flow API" from "doc/guides/nics/*" as well. Not specific to this patch, Probably we need to add a new matrix to enumerate PATTERN and ACTIONS supported by each PMD as a rte_flow feature matrix. That some else can take it up if everyone agrees the semantics.
