On Fri, Apr 10, 2020 at 6:04 PM Thomas Monjalon <tho...@monjalon.net> wrote: > > 10/04/2020 14:10, Jerin Jacob: > > On Fri, Apr 10, 2020 at 3:00 PM Ferruh Yigit <ferruh.yi...@intel.com> wrote: > > > > > > "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. > > > > > > Signed-off-by: Ferruh Yigit <ferruh.yi...@intel.com> > > > > Since you are changing "Flow API" to "Packet filtering via Flow API" > > to all the .rst file, > > Could update doc/guides/nics/octeontx2.rst, From "Generic flow API" to > > "Packet filtering via Flow API" > > Wait > rte_flow is not only about filtering. > rte_flow can configure any flow-related offload, > including encapsulation or header update.
Agree. Then it better to change to "Generic flow API" in all the docs. > >
