From: Akhil Goyal <gakhil@marvell.com>
To: Matan Azrad <matan@nvidia.com>,
Declan Doherty <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [EXT] [PATCH] cryptodev: extend data-unit length field
Date: Sat, 16 Oct 2021 14:47:39 +0000 [thread overview]
Message-ID: <CO6PR18MB4484AC53C874B28CEABD6787D8BA9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20211004063638.1977857-1-matan@nvidia.com>
> As described in [1] and as announced in [2], The field ``dataunit_len``
> of the ``struct rte_crypto_cipher_xform`` moved to the end of the
> structure and extended to ``uint32_t``.
>
> In this way, sizes bigger than 64K bytes can be supported for data-unit
> lengths.
>
> [1] commit d014dddb2d69 ("cryptodev: support multiple cipher
> data-units")
> [2] commit 9a5c09211b3a ("doc: announce extension of crypto data-unit
> length")
>
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> ---
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-10-16 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 6:36 [dpdk-dev] " Matan Azrad
2021-10-16 12:36 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-16 14:47 ` 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=CO6PR18MB4484AC53C874B28CEABD6787D8BA9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
/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).