From: "Ji, Kai" <kai.ji@intel.com>
To: Akhil Goyal <gakhil@marvell.com>,
"Leung, Michael" <michael.leung@bloombase.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [EXT] [PATCH] crypto/openssl: add aes-xts support
Date: Thu, 15 Jun 2023 16:45:57 +0000 [thread overview]
Message-ID: <SN6PR11MB3408B24B837C9F6DDAB892CC815BA@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448461776F1530AB93467B5BD85AA@CO6PR18MB4484.namprd18.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Please take time to address Akhill's comments.
Acked-by: Kai Ji <kai.ji@intel.com<mailto:kai.ji@intel.com>>
________________________________
From: Akhil Goyal <gakhil@marvell.com>
Sent: 14 June 2023 19:51
To: Leung, Michael <michael.leung@bloombase.com>; dev@dpdk.org <dev@dpdk.org>; Ji, Kai <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH] crypto/openssl: add aes-xts support
++Kai for review.
> -----Original Message-----
> From: Akhil Goyal
> Sent: Thursday, June 15, 2023 12:21 AM
> To: Michael Leung <michael.leung@bloombase.com>; dev@dpdk.org
> Subject: RE: [EXT] [PATCH] crypto/openssl: add aes-xts support
>
> > Add aes-128-xts and aes-256-xts support for crypto openssl pmd. As xts mode
> > we got 2 key, the key length is multiplied by two, i.e. 32 and 64.
> >
> > Signed-off-by: Michael Leung <michael.leung@bloombase.com>
> > ---
> Fix checkpatch issues
> Also update doc/guides/cryptodevs/features/openssl.ini
[-- Attachment #2: Type: text/html, Size: 2468 bytes --]
prev parent reply other threads:[~2023-06-15 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 23:09 Michael Leung
2023-06-14 18:50 ` [EXT] " Akhil Goyal
2023-06-14 18:51 ` Akhil Goyal
2023-06-15 16:45 ` Ji, Kai [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=SN6PR11MB3408B24B837C9F6DDAB892CC815BA@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=michael.leung@bloombase.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).