DPDK usage discussions
 help / color / mirror / Atom feed
From: Maayan Kashani <mkashani@nvidia.com>
To: Artemii Morozov <Artemii.Morozov@arknetworks.am>,
	"users@dpdk.org" <users@dpdk.org>
Cc: Asaf Penso <asafp@nvidia.com>, Matan Azrad <matan@nvidia.com>,
	"Gal Cohen (ProdM)" <galco@nvidia.com>
Subject: RE: mlx5_crypto: failed to switch to crypto operational mode
Date: Thu, 7 Sep 2023 10:29:47 +0000	[thread overview]
Message-ID: <IA1PR12MB75446143063DD39BC3E94BA6B2EEA@IA1PR12MB7544.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c828b350-76af-eaee-d736-e4c602f8e79f@arknetworks.am>

Hi, 
Sorry for the late response,
This NIC does not support crypto.

Regards,
Maayan Kashani

> -----Original Message-----
> From: Artemii Morozov <Artemii.Morozov@arknetworks.am>
> Sent: Monday, 10 July 2023 10:37
> To: users@dpdk.org
> Subject: mlx5_crypto: failed to switch to crypto operational mode
> 
> External email: Use caution opening links or attachments
> 
> 
> Hi,
> 
> I have ConnectX-6 (MCX653106A-HDAT) NIC and try to use DPDK mlx5_crypto
> driver for crypto offload. I've followed the instructions provided in the
> documentation (https://doc.dpdk.org/guides/cryptodevs/mlx5.html),
> but unfortunately, I've encountered some problems along the way.
> 
> The main issue I am experiencing is the inability to switch the NIC to crypto
> operational mode. I am facing a failure in the first step:
> 
> ```
> mlxreg -d /dev/mst/mt4123_pciconf0 --reg_name CRYPTO_OPERATIONAL --
> get Sending access register...
> -E- Failed to send access register: ME_ICMD_OPERATIONAL_ERROR ```
> 
> I use:
> - MLX_OFED 5.8-2.0.3.0
> - fw 20.35.2000
> - I set the CRYPTO_POLICY configuration value to 2 (it also does not work with 1
> value)
> 
> lsmod | grep mlx output:
> 
> ```
> mlx5_ib               450560  0
> mlx5_core            2039808  1 mlx5_ib
> mlxdevm               176128  1 mlx5_core
> ib_uverbs             143360  2 rdma_ucm,mlx5_ib
> psample                20480  1 mlx5_core
> mlxfw                  32768  1 mlx5_core
> tls                   114688  1 mlx5_core
> pci_hyperv_intf        16384  1 mlx5_core
> ib_core               434176  8
> rdma_cm,ib_ipoib,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
> mlx_compat             69632  11
> rdma_cm,ib_ipoib,mlxdevm,iw_cm,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx
> 5_ib,ib_cm,mlx5_core
> 
> ```
> 
> Could you please advise me how to solve the problem and what steps to take to
> successfully use this driver?
> 
> Thank you.


      reply	other threads:[~2023-09-07 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  7:36 Artemii Morozov
2023-09-07 10:29 ` Maayan Kashani [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=IA1PR12MB75446143063DD39BC3E94BA6B2EEA@IA1PR12MB7544.namprd12.prod.outlook.com \
    --to=mkashani@nvidia.com \
    --cc=Artemii.Morozov@arknetworks.am \
    --cc=asafp@nvidia.com \
    --cc=galco@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=users@dpdk.org \
    /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).