From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
dev@dpdk.org, Akhil Goyal <gakhil@marvell.com>,
Chenbo Xia <chenbox@nvidia.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Jay Zhou <jianjay.zhou@huawei.com>
Cc: jerinj@marvell.com, anoobj@marvell.com
Subject: Re: [v3] vhost: include AKCIPHER algorithms in crypto_config
Date: Thu, 6 Feb 2025 09:56:33 +0100 [thread overview]
Message-ID: <01e9c589-d22e-4e9a-8295-8d0c56b466ef@redhat.com> (raw)
In-Reply-To: <20250107182551.2141-1-gmuthukrishn@marvell.com>
On 1/7/25 7:25 PM, Gowrishankar Muthukrishnan wrote:
> Update virtio_crypto_config structure to include AKCIPHER algorithms,
> as per VirtIO standard.
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
> ---
> v3:
> - rebased on main.
>
> lib/vhost/virtio_crypto.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/vhost/virtio_crypto.h b/lib/vhost/virtio_crypto.h
> index e3b93573c8..28877a5da3 100644
> --- a/lib/vhost/virtio_crypto.h
> +++ b/lib/vhost/virtio_crypto.h
> @@ -410,7 +410,7 @@ struct virtio_crypto_config {
> uint32_t max_cipher_key_len;
> /* Maximum length of authenticated key */
> uint32_t max_auth_key_len;
> - uint32_t reserve;
> + uint32_t akcipher_algo;
> /* Maximum size of each crypto request's content */
> uint64_t max_size;
> };
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
prev parent reply other threads:[~2025-02-06 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 8:34 [PATCH v1] " Gowrishankar Muthukrishnan
2024-11-19 8:41 ` [PATCH v2] " Gowrishankar Muthukrishnan
2024-11-19 9:52 ` Akhil Goyal
2025-01-07 18:25 ` [v3] " Gowrishankar Muthukrishnan
2025-02-06 8:56 ` Maxime Coquelin [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=01e9c589-d22e-4e9a-8295-8d0c56b466ef@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=anoobj@marvell.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@marvell.com \
--cc=jianjay.zhou@huawei.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).