From: Akhil Goyal <gakhil@marvell.com>
To: Raja Zidane <rzidane@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>
Subject: RE: [EXT] [PATCH V5] crypto/mlx5: support BF2 and ConnectX6-DX devices
Date: Fri, 12 Nov 2021 08:43:19 +0000 [thread overview]
Message-ID: <PH0PR18MB4491A7A2B1640C117BA8F864D8959@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20211111135133.2367-1-rzidane@nvidia.com>
> Starting from FW version xx.32.0108. version, the BlueField2 and
> ConnextX6-DX adapters support crypto operations.
>
> Add them to the supported PCI devices list.
>
> Signed-off-by: Raja Zidane <rzidane@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Tal Shnaiderman <talshn@nvidia.com>
> ---
> V2: fixed checkpatch warning.
> V3: fixed doc.
> V4: fixed commit log.
> V5: fixed doc.
> doc/guides/cryptodevs/mlx5.rst | 11 ++++++++++-
> doc/guides/rel_notes/release_21_11.rst | 1 +
> drivers/crypto/mlx5/mlx5_crypto.c | 8 ++++++++
> 3 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/cryptodevs/mlx5.rst
> b/doc/guides/cryptodevs/mlx5.rst
> index 9bd8c6fe85..af85fd2f8f 100644
> --- a/doc/guides/cryptodevs/mlx5.rst
> +++ b/doc/guides/cryptodevs/mlx5.rst
> @@ -88,6 +88,7 @@ The mlxreg dedicated tool should be used as follows:
> should not be specified.
>
> All the device ports should set it in order to move to operational mode.
> + For BlueField2, the internal ports in the ARMs system should also be set.
Changed ARMs -> ARM as reported by spell check.
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-11-12 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 16:22 [dpdk-dev] [PATCH] " Raja Zidane
2021-11-07 16:26 ` Raja Zidane
2021-11-07 17:29 ` [dpdk-dev] [PATCH V2] " Raja Zidane
2021-11-07 17:44 ` Thomas Monjalon
2021-11-07 19:03 ` Tal Shnaiderman
2021-11-08 13:18 ` [dpdk-dev] [PATCH V3] " Raja Zidane
2021-11-08 14:03 ` Tal Shnaiderman
2021-11-10 12:27 ` [dpdk-dev] [PATCH V4] " Raja Zidane
2021-11-10 12:47 ` Tal Shnaiderman
2021-11-11 11:11 ` [EXT] " Akhil Goyal
2021-11-11 13:51 ` [PATCH V5] " Raja Zidane
2021-11-12 8:43 ` Akhil Goyal [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=PH0PR18MB4491A7A2B1640C117BA8F864D8959@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rzidane@nvidia.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).