When removing the documentation for the obsolete flow filtering,
the related section was kept almost empty.
It can be safely removed.
Fixes: 5007ac13189d ("ethdev: remove deprecated Flow Director configuration")
Cc: sta...@dpdk.org
Signed-off-by: Thomas Monjalon <tho...@monjalon.net>
---
v2: remove a reference to the removed section
---
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 2fbf9220d8..c99f8bc547 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -2919,14 +2919,6 @@ for port 0 and queue 0::
testpmd> set port cman config 0 0 obj queue mode red 10 100 1
-Filter Functions
-----------------
-
-This section details the available filter functions that are available.
-
-Note these functions interface the deprecated legacy filtering framework,
-superseded by *rte_flow*. See `Flow rules management`_.
-
.. _testpmd_rte_flow:
Flow rules management
@@ -2936,10 +2928,6 @@ Control of the generic flow API (*rte_flow*) is fully
exposed through the
``flow`` command (configuration, validation, creation, destruction, queries
and operation modes).
-Considering *rte_flow* overlaps with all `Filter Functions`_, using both
-features simultaneously may cause undefined side-effects and is therefore
-not recommended.
-
``flow`` syntax
~~~~~~~~~~~~~~~
--
2.45.0
