From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [dpdk-dev v2] crypto/aesni_gcm: fix performance issue
Date: Wed, 7 Jul 2021 13:36:53 +0000 [thread overview]
Message-ID: <CO6PR18MB44848833F091609E4CE62F99D81A9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BL0PR11MB30437081006CC62504CC4C51B8029@BL0PR11MB3043.namprd11.prod.outlook.com>
> >
> > This patch fixes the aesni_gcm performance issue on systems with AVX512
> > CPU flag presented but with VAES CPU flag missing, such as Skylake.
> >
> > Fixes: 81fe96a0cece ("crypto/aesni_gcm: use architecture independent
> API")
> > Cc: pablo.de.lara.guarch@intel.com
> >
> > Signed-off-by: Kai Ji <kai.ji@intel.com>
>
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2021-07-07 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 12:36 [dpdk-dev] [dpdk-dev v1] " Kai Ji
2021-06-29 15:19 ` [dpdk-dev] [dpdk-dev v2] " Kai Ji
2021-06-29 15:25 ` Zhang, Roy Fan
2021-07-07 13:36 ` 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=CO6PR18MB44848833F091609E4CE62F99D81A9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@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).