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>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/aesni_gcm: use architecture independent API
Date: Tue, 16 Apr 2019 14:55:22 +0000	[thread overview]
Message-ID: <VI1PR04MB4893DDF7A0540B4AADE89AFEE6240@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190416145522.8KG6uvG2FiqwzJJMLxa5na8Qa9eDu_jEo9Q-e3b3R3o@z> (raw)


> 
> 
> IPSec Multi-buffer library has recently added API
> that sets pointers depending on the architecture, at initiliazation,
> in version 0.52.
> 
> AESNI MB PMD was updated with these changes, but not
> the AESNI GCM PMD, which also uses the same library.
> 
> This makes the PMD to be only compatible with version 0.52,
> but makes both PMD consistent on version compatibility,
> plus adds support for AVX512.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>  doc/guides/cryptodevs/aesni_gcm.rst           |  9 ++-
>  doc/guides/cryptodevs/features/aesni_gcm.ini  |  1 +
>  drivers/crypto/aesni_gcm/aesni_gcm_ops.h      | 66 +++-------------
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd.c      | 77 ++++++++++++++++---
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c  |  4 +-
>  .../crypto/aesni_gcm/aesni_gcm_pmd_private.h  |  6 +-
>  6 files changed, 89 insertions(+), 74 deletions(-)
> 
Applied to dpdk-next-crypto

Thanks.

             reply	other threads:[~2019-04-16 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 14:55 Akhil Goyal [this message]
2019-04-16 14:55 ` Akhil Goyal
  -- strict thread matches above, loose matches on Subject: below --
2019-04-10  0:41 Pablo de Lara
2019-04-10  0:41 ` Pablo de Lara

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=VI1PR04MB4893DDF7A0540B4AADE89AFEE6240@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=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).