DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] crypto/aesni_gcm: allow device init if no	AES-NI is present
Date: Mon, 21 Oct 2019 08:51:01 +0000	[thread overview]
Message-ID: <VE1PR04MB6639EDFB716D81DE78BBDC84E6690@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1571329850-241335-2-git-send-email-pablo.de.lara.guarch@intel.com>



> 
> The IPSec Multi buffer library does not require AES-NI
> instructions to be supported by the CPU, as it can emulate these
> instructions in software (adding a big performance penalty when
> using AES algorithms).
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> v2:
> - Fixed leading whitespaces
> 
Series applied to dpdk-next-crypto

Thanks.



      reply	other threads:[~2019-10-21  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 16:20 [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: " Pablo de Lara
2019-10-17 16:20 ` [dpdk-dev] [PATCH 2/2] crypto/aesni_gcm: " Pablo de Lara
2019-10-17 16:30 ` [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: " Pablo de Lara
2019-10-17 16:30   ` [dpdk-dev] [PATCH v2 2/2] crypto/aesni_gcm: " Pablo de Lara
2019-10-21  8:51     ` 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=VE1PR04MB6639EDFB716D81DE78BBDC84E6690@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.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).