DPDK usage discussions
 help / color / mirror / Atom feed
From: Artemii Morozov <Artemii.Morozov@arknetworks.am>
To: users@dpdk.org
Subject: mlx5_crypto: failed to switch to crypto operational mode
Date: Mon, 10 Jul 2023 11:36:42 +0400	[thread overview]
Message-ID: <c828b350-76af-eaee-d736-e4c602f8e79f@arknetworks.am> (raw)


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-
- 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 
mlx_compat             69632  11 


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-07-10  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  7:36 Artemii Morozov [this message]
2023-09-07 10:29 ` Maayan Kashani

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c828b350-76af-eaee-d736-e4c602f8e79f@arknetworks.am \
    --to=artemii.morozov@arknetworks.am \
    --cc=users@dpdk.org \


* 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).