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 BB160A04BC; Thu, 8 Oct 2020 15:42:52 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6B55B1C121; Thu, 8 Oct 2020 15:42:40 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by dpdk.org (Postfix) with ESMTP id A8D741C11D for ; Thu, 8 Oct 2020 15:42:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1602164557; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=e7dIC8uc2woFW6ozOd7bav5rRoRVDhEGHpIbQVrjBos=; b=eSIxsKqN4wzlphYLfxWVNbQW8XxgVQsfTfDSxmABVZIzfLQGffbit18vI0qCFuq5VCEwaG MMgkEZFvwloujIaTOy3Xk8RWMDDJTcJibSell1/B8pDKMvRvYJEpleXbv1/2jGroZpRcjm qsicF/pHdZLFK3xXQOuLKAUj39wylK0= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-188-w4l9920DN_SBlFJyvp81vw-1; Thu, 08 Oct 2020 09:42:35 -0400 X-MC-Unique: w4l9920DN_SBlFJyvp81vw-1 Received: by mail-vk1-f200.google.com with SMTP id v129so1048349vke.23 for ; Thu, 08 Oct 2020 06:42:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=e7dIC8uc2woFW6ozOd7bav5rRoRVDhEGHpIbQVrjBos=; b=F7bdvtRqGZU2QJ/TAbXbqYqjW3eb/AWTBqjmmlkZeWhsqe/WHtCdQWgGWq7+N61NIu nrCMkeF8X6AxkTmHCb2JcPTxqhtxa6eBUMxwx6M2EKOTM0rN4+3QQwsTXzCHbH7Kke90 5c9bQpxhFW1RCF8OsdxkkncjpC/mGUPJUuPDXowcfUT8+7eSbVjaRZP00WE7E+wYPfll z4ke184Z0kJKJzQ9Je1RvERERXC0ifuYbahEoEkFWL7Bmtbggb0s3rWC5ZLDataV4he/ 3SF8D4VomZXC7f6QvalE1ANcYRLbdlpoZ9KcJGZ09VfxM+WU4d2hZlt7POT3/NLDDRVF KOoQ== X-Gm-Message-State: AOAM530aje+UVwaVmWlZnPJMLrZavXIT27QwTNpckzfAC43LsKXzdhss tqg0gA37weCmmzYwDlaYsnl1EFkTBAx27h6I5zeaKFQa6n+SbjUvDC0Dr8TStk/Sk/WfmlrBCnb CQ0VC+4MRQLL74ZtUyaY= X-Received: by 2002:ab0:a94:: with SMTP id d20mr4393703uak.86.1602164555055; Thu, 08 Oct 2020 06:42:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxbnTW+FHNbj+NHKZObdF3TX2t2+TG3dGf5qQ9/GEOMq8iRUDkkJpiyCJ8VJhluLqfRvS3PctvC2Xu52dz3TeU= X-Received: by 2002:ab0:a94:: with SMTP id d20mr4393680uak.86.1602164554789; Thu, 08 Oct 2020 06:42:34 -0700 (PDT) MIME-Version: 1.0 References: <20201005184526.7465-1-konstantin.ananyev@intel.com> <20201006150316.5776-1-konstantin.ananyev@intel.com> <20201006150316.5776-3-konstantin.ananyev@intel.com> In-Reply-To: <20201006150316.5776-3-konstantin.ananyev@intel.com> From: David Marchand Date: Thu, 8 Oct 2020 15:42:23 +0200 Message-ID: To: Konstantin Ananyev Cc: dev , Jerin Jacob Kollanukkaran , "Ruifeng Wang (Arm Technology China)" , Vladimir Medvedkin , dpdk stable Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [PATCH v4 02/14] doc: fix missing 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" On Tue, Oct 6, 2020 at 5:09 PM Konstantin Ananyev wrote: > > 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/g= uides/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 algori= thm: > > * **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 buil= d-time difference. > All implementations operates over the same internal RT structures and us= e similar principles. The main difference is that vector implementations ca= n manually exploit IA SIMD instructions and process several input data flow= s 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 a= bility to override the default classifier function for a given ACL context = or perform particular search using non-default classify method. In that cas= e it is user responsibility to make sure that given platform supports selec= ted classify implementation. > -- > 2.17.1 > Reviewed-by: David Marchand --=20 David Marchand