Add brief description for missing ACL classify algorithms:
RTE_ACL_CLASSIFY_NEON and RTE_ACL_CLASSIFY_ALTIVEC.
Fixes: 34fa6c27c156 ("acl: add NEON optimization for ARMv8")
Fixes: 1d73135f9f1c ("acl: add AltiVec for ppc64")
Cc: sta...@dpdk.org
Signed-off-by: Konstantin Ananyev <konstantin.anan...@intel.com>
---
doc/guides/prog_guide/packet_classif_access_ctrl.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/prog_guide/packet_classif_access_ctrl.rst
b/doc/guides/prog_guide/packet_classif_access_ctrl.rst
index 0345512b9..daf03e6d7 100644
--- a/doc/guides/prog_guide/packet_classif_access_ctrl.rst
+++ b/doc/guides/prog_guide/packet_classif_access_ctrl.rst
@@ -373,6 +373,12 @@ There are several implementations of classify algorithm:
* **RTE_ACL_CLASSIFY_AVX2**: vector implementation, can process up to 16
flows in parallel. Requires AVX2 support.
+* **RTE_ACL_CLASSIFY_NEON**: vector implementation, can process up to 8 flows
+ in parallel. Requires NEON support.
+
+* **RTE_ACL_CLASSIFY_ALTIVEC**: vector implementation, can process up to 8
+ flows in parallel. Requires ALTIVEC support.
+
It is purely a runtime decision which method to choose, there is no build-time
difference.
All implementations operates over the same internal RT structures and use
similar principles. The main difference is that vector implementations can
manually exploit IA SIMD instructions and process several input data flows in
parallel.
At startup ACL library determines the highest available classify method for
the given platform and sets it as default one. Though the user has an ability
to override the default classifier function for a given ACL context or perform
particular search using non-default classify method. In that case it is user
responsibility to make sure that given platform supports selected classify
implementation.
--
2.17.1
