"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> --- Cc: Thomas Monjalon <tho...@monjalon.net> Cc: Andrew Rybchenko <arybche...@solarflare.com> Cc: Adrien Mazarguil <adrien.mazarg...@6wind.com> Cc: Ajit Khaparde <ajit.khapa...@broadcom.com> Cc: Jerin Jacob <jer...@marvell.com> --- doc/guides/nics/features/default.ini | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/guides/nics/features/default.ini b/doc/guides/nics/features/default.ini index ca3b738ea..192a5168e 100644 --- a/doc/guides/nics/features/default.ini +++ b/doc/guides/nics/features/default.ini @@ -45,7 +45,6 @@ Flexible filter = Hash filter = Flow director = Flow control = -Flow API = Rate limitation = Traffic mirroring = Inline crypto = -- 2.21.0
