From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <viktorin@rehivetech.com>
Received: from wes1-so1.wedos.net (wes1-so1-b.wedos.net [46.28.106.43])
 by dpdk.org (Postfix) with ESMTP id E323C7CB8
 for <dev@dpdk.org>; Thu,  4 May 2017 17:21:42 +0200 (CEST)
Received: from pcviktorin.fit.vutbr.cz (dhcpz185.fit.vutbr.cz [147.229.14.185])
 by wes1-so1.wedos.net (Postfix) with ESMTPSA id 3wJdzV3Q5fz1pf;
 Thu,  4 May 2017 17:21:42 +0200 (CEST)
Date: Thu, 4 May 2017 17:20:22 +0200
From: Jan Viktorin <viktorin@rehivetech.com>
To: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
Cc: cristian.dumitrescu@intel.com, thomas@monjalon.net,
 jasvinder.singh@intel.com, jerin.jacob@caviumnetworks.com,
 jianbo.liu@linaro.org, dev@dpdk.org
Message-ID: <20170504172022.1af906b8.viktorin@rehivetech.com>
In-Reply-To: <20170504065702.22404-1-ashwin.sekhar@caviumnetworks.com>
References: <20170427140618.35897-1-ashwin.sekhar@caviumnetworks.com>
 <20170504065702.22404-1-ashwin.sekhar@caviumnetworks.com>
Organization: RehiveTech
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH v3 1/4] mk: add crypto capability for generic
 armv8a and thunderx
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 04 May 2017 15:21:43 -0000

On Wed,  3 May 2017 23:56:59 -0700
Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com> wrote:

> armv8-a has optional CRYPTO extension which adds the
> AES, PMULL, SHA1 and SHA2 capabilities. -march=armv8-a+crypto
> enables code generation for the ARMv8-A architecture together
> with the optional CRYPTO extensions.
> 
> added the following flags to detect the corresponding
> capability at compile time
>  * RTE_MACHINE_CPUFLAG_AES
>  * RTE_MACHINE_CPUFLAG_PMULL
>  * RTE_MACHINE_CPUFLAG_SHA1
>  * RTE_MACHINE_CPUFLAG_SHA2
> 
> at run-time, the following flags can be used to detect these
> capabilities
>  * RTE_CPUFLAG_AES
>  * RTE_CPUFLAG_PMULL
>  * RTE_CPUFLAG_SHA1
>  * RTE_CPUFLAG_SHA2
> 
> Signed-off-by: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>

Reviewed-by: Jan Viktorin <viktorin@rehivetech.com>