DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-crypto 19.05 rc3
Date: Wed,  1 May 2019 19:56:20 +0530	[thread overview]
Message-ID: <20190501142620.12061-1-akhil.goyal@nxp.com> (raw)

The following changes since commit 7f251bcf22c5729792f9243480af1b3c072876a5:

  version: 19.05-rc2 (2019-04-23 00:43:52 +0200)

are available in the Git repository at:

  http://dpdk.org/git/next/dpdk-next-crypto 

for you to fetch changes up to 035c9fb61cb3d1053bdb291d45a0ca13a69230f6:

  doc/crypto: add release notes and updates for qat PMD (2019-05-01 19:42:47 +0530)

----------------------------------------------------------------
Akhil Goyal (1):
      examples/ipsec-secgw: fix pool usage for security session

Anoob Joseph (1):
      crypto/octeontx: use distinct metabuf pool for each queue

Arek Kusztal (1):
      doc/crypto: add release notes and updates for qat PMD

Ayuj Verma (1):
      crypto: include dependency in asym header

Bruce Richardson (3):
      crypto/aesni_gcm: add dependency version check
      crypto/aesni_mb: cleanup of version check code
      crypto/aesni_gcm: add check for build dependency

Fiona Trahe (1):
      crypto/qat: fix NULL cipher algo for non 8-byte multiple

Konstantin Ananyev (1):
      examples/ipsec-secgw: fix SPD no-match is misinterpreted

 doc/guides/cryptodevs/features/qat.ini            |   2 +
 doc/guides/cryptodevs/qat.rst                     |  81 ++++++++++++-----
 doc/guides/rel_notes/release_19_05.rst            |   6 ++
 drivers/common/cpt/cpt_common.h                   |  10 ++-
 drivers/common/cpt/cpt_ucode.h                    |  24 +++--
 drivers/crypto/aesni_gcm/Makefile                 |  19 +++-
 drivers/crypto/aesni_gcm/meson.build              |  11 +++
 drivers/crypto/aesni_mb/meson.build               |  18 ++--
 drivers/crypto/octeontx/otx_cryptodev.c           |   3 -
 drivers/crypto/octeontx/otx_cryptodev_hw_access.c | 105 ++++++++++++++++++++--
 drivers/crypto/octeontx/otx_cryptodev_hw_access.h |   7 +-
 drivers/crypto/octeontx/otx_cryptodev_ops.c       |  98 ++------------------
 drivers/crypto/octeontx/otx_cryptodev_ops.h       |   3 -
 drivers/crypto/qat/qat_sym_session.c              |   3 +-
 examples/ipsec-secgw/ipsec-secgw.c                |  25 +++---
 examples/ipsec-secgw/ipsec.c                      |   4 +-
 examples/ipsec-secgw/ipsec.h                      |  14 ++-
 examples/ipsec-secgw/sa.c                         |  35 ++++++--
 examples/ipsec-secgw/sp4.c                        |  49 +++++++++-
 examples/ipsec-secgw/sp6.c                        |  49 +++++++++-
 lib/librte_cryptodev/rte_crypto_asym.h            |   2 +
 21 files changed, 380 insertions(+), 188 deletions(-)

             reply	other threads:[~2019-05-01 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 14:26 Akhil Goyal [this message]
2019-05-01 14:26 ` Akhil Goyal
2019-05-01 21:07 ` Thomas Monjalon
2019-05-01 21:07   ` Thomas Monjalon

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=20190501142620.12061-1-akhil.goyal@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).