From: Akhil Goyal <gakhil@marvell.com>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v3 0/2] crypto/mlx5: optimize AES-GCM IPsec operation
Date: Wed, 26 Jun 2024 06:49:27 +0000 [thread overview]
Message-ID: <CO6PR18MB44849F4D230263E10B4A3579D8D62@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240624091651.2295533-1-suanmingm@nvidia.com>
> To optimize AES-GCM IPsec operation within crypto/mlx5,
> the DPDK API typically supplies AES_GCM AAD/Payload/Digest
> in separate locations, potentially disrupting their
> contiguous layout. In cases where the memory layout fails
> to meet hardware (HW) requirements, an UMR WQE is initiated
> ahead of the GCM's GGA WQE to establish a continuous
> AAD/Payload/Digest virtual memory space for the HW MMU.
>
> For IPsec scenarios, where the memory layout consistently
> adheres to the fixed order of AAD/IV/Payload/Digest,
> directly shrinking memory for AAD proves more efficient
> than preparing a UMR WQE. To address this, a new devarg
> "crypto_mode" with mode "ipsec_opt" is introduced in the
> commit, offering an optimization hint specifically for
> IPsec cases. When enabled, the PMD copies AAD directly
> before Payload in the enqueue_burst function instead of
> employing the UMR WQE. Subsequently, in the dequeue_burst
> function, the overridden IV before Payload is restored
> from the GGA WQE. It's crucial for users to avoid utilizing
> the input mbuf data during processing.
>
>
> v3: add limitation for non-contiguous inputs.
> v2: rebase version
>
> Suanming Mou (2):
> crypto/mlx5: optimize AES-GCM IPsec operation
> crypto/mlx5: add out of place mode for IPsec operation
>
> doc/guides/cryptodevs/mlx5.rst | 24 +++
> doc/guides/rel_notes/release_24_07.rst | 4 +
> drivers/crypto/mlx5/mlx5_crypto.c | 22 ++-
> drivers/crypto/mlx5/mlx5_crypto.h | 19 ++
> drivers/crypto/mlx5/mlx5_crypto_gcm.c | 245
> +++++++++++++++++++++++--
> 5 files changed, 293 insertions(+), 21 deletions(-)
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2024-06-26 6:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 7:24 [PATCH " Suanming Mou
2024-05-30 7:24 ` [PATCH 1/2] " Suanming Mou
2024-05-30 7:24 ` [PATCH 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-13 6:44 ` [PATCH 0/2] crypto/mlx5: optimize AES-GCM " Suanming Mou
2024-06-13 18:02 ` Akhil Goyal
2024-06-14 0:30 ` Suanming Mou
2024-06-14 0:30 ` [PATCH v2 " Suanming Mou
2024-06-14 0:30 ` [PATCH v2 1/2] " Suanming Mou
2024-06-14 6:49 ` [EXTERNAL] " Akhil Goyal
2024-06-14 7:15 ` Suanming Mou
2024-06-14 9:06 ` Akhil Goyal
2024-06-14 9:32 ` Suanming Mou
2024-06-18 6:47 ` Suanming Mou
2024-06-20 7:40 ` Akhil Goyal
2024-06-20 8:16 ` Suanming Mou
2024-06-20 9:06 ` Akhil Goyal
2024-06-20 9:41 ` Suanming Mou
2024-06-24 8:27 ` Akhil Goyal
2024-06-24 8:41 ` Suanming Mou
2024-06-24 8:44 ` Akhil Goyal
2024-06-24 8:52 ` Suanming Mou
2024-06-14 0:30 ` [PATCH v2 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 0/2] crypto/mlx5: optimize AES-GCM " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 1/2] " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-26 6:49 ` 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=CO6PR18MB44849F4D230263E10B4A3579D8D62@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=suanmingm@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).