From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>, Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] doc: update build guide for armv8 crypto PMD
Date: Wed, 14 Oct 2020 14:10:17 +0000 [thread overview]
Message-ID: <DBAPR08MB5814E78F84B4C918FE8D5DA598050@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20201014092414.9532-1-ruifeng.wang@arm.com>
<snip>
>
> Removed references to Makefile and added guide about building by using
> meson.
>
> Also added the command to create virtual device.
>
> Suggested-by: Akhil Goyal <akhil.goyal@nxp.com>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> ---
> doc/guides/cryptodevs/armv8.rst | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/doc/guides/cryptodevs/armv8.rst
> b/doc/guides/cryptodevs/armv8.rst index fee85354b..d11efe08d 100644
> --- a/doc/guides/cryptodevs/armv8.rst
> +++ b/doc/guides/cryptodevs/armv8.rst
> @@ -26,22 +26,23 @@ Supported authentication algorithms:
> Installation
> ------------
>
> -In order to enable this virtual crypto PMD, user must:
> +To build DPDK with this virtual crypto PMD, the user is required to:
>
> * Download AArch64 crypto library source code from
> - `here <https://github.com/ARM-software/AArch64cryptolib>`_
> + `here <https://github.com/ARM-software/AArch64cryptolib>`_.
>
> -* Export the environmental variable ARMV8_CRYPTO_LIB_PATH with
> - the path to ``AArch64cryptolib`` library.
> -
> -* Build the library by invoking:
> +* Build the ``AArch64cryptolib`` library:
>
> .. code-block:: console
>
> - make -C $ARMV8_CRYPTO_LIB_PATH/
> + make
> +
> +* Build DPDK with meson option ``-
> Darmv8_crypto_dir=<path_to_AArch64cryptolib>``:
> +
> +.. code-block:: console
>
> -* Set CONFIG_RTE_LIBRTE_PMD_ARMV8_CRYPTO=y in
How is the flag set for Meson? Does it need to be documented here?
> - config/defconfig_arm64-armv8a-linux-gcc
> + meson -Darmv8_crypto_dir=<path_to_AArch64cryptolib> build
> + ninja -C build
>
> The corresponding device can be created only if the following features are
> supported by the CPU:
> @@ -53,6 +54,7 @@ are supported by the CPU:
>
> Initialization
> --------------
> +Use ``--vdev "crypto_armv8"`` in the EAL options to create virtual crypto
> device.
>
> User can use app/test application to check how to use this PMD and to verify
> crypto processing.
> --
> 2.17.1
next prev parent reply other threads:[~2020-10-14 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 9:24 Ruifeng Wang
2020-10-14 14:10 ` Honnappa Nagarahalli [this message]
2020-10-14 14:19 ` Ruifeng Wang
2020-10-14 14:24 ` Honnappa Nagarahalli
2020-10-22 21:10 ` Thomas Monjalon
2020-10-22 21:17 ` Thomas Monjalon
2020-10-22 21:25 ` Honnappa Nagarahalli
2020-10-27 4:18 ` Dharmik Thakkar
2020-10-27 8:45 ` Thomas Monjalon
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=DBAPR08MB5814E78F84B4C918FE8D5DA598050@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
/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).