From: Akhil Goyal <gakhil@marvell.com>
To: Raja Zidane <rzidane@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "matan@nvidia.com" <matan@nvidia.com>
Subject: RE: [EXT] [PATCH 1/2] common/mlx5: extend crypto capabilities
Date: Mon, 25 Apr 2022 05:27:39 +0000 [thread overview]
Message-ID: <CO6PR18MB44841AA52B9D4910C8793E69D8F89@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220418111005.2291-2-rzidane@nvidia.com>
> +struct mlx5_ifc_crypto_caps_bits {
> + u8 wrapped_crypto_operational[0x1];
> + u8 wrapped_crypto_going_to_commissioning[0x1];
> + u8 sw_wrapped_dek[0x1];
> + u8 synchronize_dek[0x1];
> + u8 int_kek_manual[0x1];
> + u8 int_kek_auto[0x1];
> + u8 reserved_at_6[0x12];
> + u8 wrapped_import_method[0x8];
> + u8 reserved_at_20[0x3];
> + u8 log_dek_max_alloc[0x5];
> + u8 reserved_at_28[0x3];
> + u8 log_max_num_deks[0x5];
> + u8 reserved_at_30[0x3];
> + u8 log_max_num_import_keks[0x5];
> + u8 reserved_at_38[0x3];
> + u8 log_max_num_creds[0x5];
> + u8 failed_selftests[0x10];
> + u8 num_nv_import_keks[0x8];
> + u8 num_nv_credentials[0x8];
> + u8 reserved_at_60[0x3];
> + u8 log_dek_granularity[0x5];
> + u8 reserved_at_68[0x3];
> + u8 log_max_num_int_kek[0x5];
> + u8 reserved_at_70[0x10];
> + u8 reserved_at_80[0x780];
> +};
Where is this structure getting used?
next prev parent reply other threads:[~2022-04-25 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 11:10 [PATCH 0/2] crypto/mlx5: add support for plaintext import method Raja Zidane
2022-04-18 11:10 ` [PATCH 1/2] common/mlx5: extend crypto capabilities Raja Zidane
2022-04-25 5:27 ` Akhil Goyal [this message]
2022-04-18 11:10 ` [PATCH 2/2] crypto/mlx5: support plaintext keys Raja Zidane
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=CO6PR18MB44841AA52B9D4910C8793E69D8F89@CO6PR18MB4484.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).