From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] support CPU crypto for AESNI MB PMD
Date: Wed, 1 Apr 2020 15:09:51 +0000 [thread overview]
Message-ID: <BN7PR11MB2547A228E28E943A833728CB9AC90@BN7PR11MB2547.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB8PR04MB6635A70D650C1282502A84DCE6C90@DB8PR04MB6635.eurprd04.prod.outlook.com>
Hi Akhil,
>
> Hi Konstantin,
>
> It looks there are some failures in meson build.
> Could you please fix them and send a v2?
Will do.
>
> Thanks,
> Akhil
>
> > -----Original Message-----
> > From: Konstantin Ananyev <konstantin.ananyev@intel.com>
> > Sent: Monday, March 16, 2020 6:51 PM
> > To: dev@dpdk.org
> > Cc: Akhil Goyal <akhil.goyal@nxp.com>; pablo.de.lara.guarch@intel.com;
> > declan.doherty@intel.com; Konstantin Ananyev
> > <konstantin.ananyev@intel.com>
> > Subject: [PATCH 0/2] support CPU crypto for AESNI MB PMD
> >
> > Add support for CPU crypto API into aesni_mb PMD
> > and extend cryptodev UT to cover this new functionality.
> >
> > Konstantin Ananyev (2):
> > crypto/aesni_mb: support CPU crypto
> > test/crypto: add CPU crypto mode for AESNI MB
> >
> > app/test/test_cryptodev.c | 146 +++++--
> > doc/guides/cryptodevs/aesni_mb.rst | 3 +
> > doc/guides/cryptodevs/features/aesni_mb.ini | 1 +
> > .../crypto/aesni_mb/aesni_mb_pmd_private.h | 5 +-
> > drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 384 ++++++++++++++++--
> > .../crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 2 +
> > 6 files changed, 476 insertions(+), 65 deletions(-)
> >
> > --
> > 2.17.1
next prev parent reply other threads:[~2020-04-01 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 13:21 Konstantin Ananyev
2020-03-16 13:21 ` [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: support CPU crypto Konstantin Ananyev
2020-03-16 13:21 ` [dpdk-dev] [PATCH 2/2] test/crypto: add CPU crypto mode for AESNI MB Konstantin Ananyev
2020-04-01 14:18 ` [dpdk-dev] [PATCH 0/2] support CPU crypto for AESNI MB PMD Akhil Goyal
2020-04-01 15:09 ` Ananyev, Konstantin [this message]
2020-04-03 15:55 ` [dpdk-dev] [PATCH v2 " Konstantin Ananyev
2020-04-03 15:55 ` [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: support CPU crypto Konstantin Ananyev
2020-04-15 9:08 ` De Lara Guarch, Pablo
2020-04-15 9:14 ` De Lara Guarch, Pablo
2020-04-15 9:52 ` Ananyev, Konstantin
2020-04-03 15:55 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: add CPU crypto mode for AESNI MB Konstantin Ananyev
2020-04-15 9:13 ` De Lara Guarch, Pablo
2020-04-15 18:25 ` Akhil Goyal
2020-04-03 16:26 ` [dpdk-dev] [PATCH v2 0/2] support CPU crypto for AESNI MB PMD Akhil Goyal
2020-04-17 15:03 ` [dpdk-dev] [PATCH v3 " Konstantin Ananyev
2020-04-17 15:03 ` [dpdk-dev] [PATCH v3 1/2] crypto/aesni_mb: support CPU crypto Konstantin Ananyev
2020-04-17 15:03 ` [dpdk-dev] [PATCH v3 2/2] test/crypto: add CPU crypto mode for AESNI MB Konstantin Ananyev
2020-04-17 20:57 ` [dpdk-dev] [PATCH v3 0/2] support CPU crypto for AESNI MB PMD Akhil Goyal
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=BN7PR11MB2547A228E28E943A833728CB9AC90@BN7PR11MB2547.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.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).