From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0D7E4A04C7; Tue, 15 Sep 2020 18:51:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B6CB71C131; Tue, 15 Sep 2020 18:51:00 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 373761C12C; Tue, 15 Sep 2020 18:50:59 +0200 (CEST) IronPort-SDR: 8qNBZJO/BTWGhjA7eUxTs025eS/SOya+Z/bmuOa4/4tcAqZ4PqzsfVgmMJyB3kDXMzloPBphbR BpmZXKrS3Wlw== X-IronPort-AV: E=McAfee;i="6000,8403,9745"; a="139310959" X-IronPort-AV: E=Sophos;i="5.76,430,1592895600"; d="scan'208";a="139310959" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Sep 2020 09:50:58 -0700 IronPort-SDR: 4jjPQJAOTEMRBhV1L4OKjeqFG/R8GgCwYV/js3VJ6pP5m+LQ0wwKWNuPm0ddL6LGMCKse3dFM5 hBPi0VyBhRhw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,430,1592895600"; d="scan'208";a="306709330" Received: from sivswdev08.ir.intel.com ([10.237.217.47]) by orsmga006.jf.intel.com with ESMTP; 15 Sep 2020 09:50:57 -0700 From: Konstantin Ananyev To: dev@dpdk.org Cc: jerinj@marvell.com, ruifeng.wang@arm.com, vladimir.medvedkin@intel.com, Konstantin Ananyev , stable@dpdk.org Date: Tue, 15 Sep 2020 17:50:15 +0100 Message-Id: <20200915165025.543-3-konstantin.ananyev@intel.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20200915165025.543-1-konstantin.ananyev@intel.com> References: <20200807162829.11690-1-konstantin.ananyev@intel.com> <20200915165025.543-1-konstantin.ananyev@intel.com> Subject: [dpdk-dev] [PATCH v2 02/12] doc: fix mixing classify methods in ACL guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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