patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: kastytis731105@gmail.com
Cc: konstantin.ananyev@intel.com, stable@dpdk.org
Subject: [dpdk-stable] [PATCH v3 02/14] doc: fix missing classify methods in ACL guide
Date: Mon,  5 Oct 2020 20:28:19 +0100	[thread overview]
Message-ID: <20201005192831.13508-3-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <20201005192831.13508-1-konstantin.ananyev@intel.com>

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: stable@dpdk.org

Signed-off-by: Konstantin Ananyev <konstantin.ananyev@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 0345512b9e..daf03e6d7a 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


      parent reply	other threads:[~2020-10-05 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200807162829.11690-1-konstantin.ananyev@intel.com>
2020-08-07 16:28 ` [dpdk-stable] [PATCH 20.11 1/7] acl: fix x86 build when compiler doesn't support AVX2 Konstantin Ananyev
     [not found] ` <20200915165025.543-1-konstantin.ananyev@intel.com>
2020-09-15 16:50   ` [dpdk-stable] [PATCH v2 01/12] " Konstantin Ananyev
2020-09-15 16:50   ` [dpdk-stable] [PATCH v2 02/12] doc: fix mixing classify methods in ACL guide Konstantin Ananyev
     [not found]   ` <20201005184526.7465-1-konstantin.ananyev@intel.com>
2020-10-05 18:45     ` [dpdk-stable] [PATCH v3 01/14] acl: fix x86 build when compiler doesn't support AVX2 Konstantin Ananyev
2020-10-05 18:45     ` [dpdk-stable] [PATCH v3 02/14] doc: fix missing classify methods in ACL guide Konstantin Ananyev
     [not found]     ` <20201006150316.5776-1-konstantin.ananyev@intel.com>
2020-10-06 15:03       ` [dpdk-stable] [PATCH v4 01/14] acl: fix x86 build when compiler doesn't support AVX2 Konstantin Ananyev
2020-10-08 13:42         ` David Marchand
2020-10-06 15:03       ` [dpdk-stable] [PATCH v4 02/14] doc: fix missing classify methods in ACL guide Konstantin Ananyev
2020-10-08 13:42         ` [dpdk-stable] [dpdk-dev] " David Marchand
     [not found]   ` <20201005192831.13508-1-konstantin.ananyev@intel.com>
2020-10-05 19:28     ` [dpdk-stable] [PATCH v3 01/14] acl: fix x86 build when compiler doesn't support AVX2 Konstantin Ananyev
2020-10-05 19:28     ` Konstantin Ananyev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201005192831.13508-3-konstantin.ananyev@intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=kastytis731105@gmail.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).