DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] next-crypto 21.05 rc1
Date: Fri, 16 Apr 2021 16:16:25 +0530	[thread overview]
Message-ID: <20210416104625.1743193-1-gakhil@marvell.com> (raw)

The following changes since commit 2414ce9b7b1770be2a5f406a1862589ebdef0315:

  power: fix closing frequency file (2021-04-15 23:53:39 +0200)

are available in the Git repository at:

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

for you to fetch changes up to df295be9d4d59261a7de76c4ee16b4ce0408d279:

  examples/l2fwd-crypto: remove key size validation (2021-04-16 16:13:33 +0530)

----------------------------------------------------------------
Adam Dybkowski (3):
      test/crypto: close PMD after tests
      app/crypto-perf: close PMD after benchmark run
      crypto/qat: support Single-Pass GMAC on QAT GEN3

Ankur Dwivedi (1):
      crypto/octeontx: fix session-less mode

Anoob Joseph (1):
      doc: update limitations of OCTEON TX crypto PMDs

Apeksha Gupta (1):
      examples/l2fwd-crypto: fix dev configure for masked devices

Arek Kusztal (1):
      crypto/qat: fix to small sgl oop min offset

Ciara Power (1):
      doc: fix dpdk-graph-crypto-perf dependencies

Fan Zhang (1):
      cryptodev: change raw data path dequeue API

Gagandeep Singh (1):
      examples/l2fwd-crypto: align private data size to cache size

Matan Azrad (2):
      cryptodev: support multiple cipher data-units
      cryptodev: formalize key wrap method in API

Nicolas Chautru (1):
      bbdev: add explicit enum for code block mode

Rohit Raj (1):
      examples/l2fwd-crypto: fix packet length while decryption

Shiri Kuzin (1):
      examples/l2fwd-crypto: remove key size validation

Tejasree Kondoj (6):
      crypto/octeontx2: remove redundant code
      common/cpt: support encrypted digest mode
      test/crypto: add cases for block cipher encrypted digest
      crypto/octeontx2: support UDP encapsulation
      examples/ipsec-secgw: support UDP encapsulation
      crypto/octeontx2: support lookaside IPv4 transport mode

 app/test-bbdev/test_bbdev_perf.c                   |  16 +-
 app/test-bbdev/test_bbdev_vector.c                 |  16 +-
 app/test-crypto-perf/main.c                        |  15 +-
 app/test/test_cryptodev.c                          |  13 +-
 app/test/test_cryptodev_aes_test_vectors.h         | 573 +++++++++++++++++++++
 app/test/test_cryptodev_blockcipher.c              |  99 +++-
 app/test/test_cryptodev_blockcipher.h              |  10 +
 devtools/libabigail.abignore                       |  12 +-
 doc/guides/cryptodevs/features/default.ini         |   2 +
 doc/guides/cryptodevs/features/octeontx.ini        |   1 +
 doc/guides/cryptodevs/features/octeontx2.ini       |   1 +
 doc/guides/cryptodevs/octeontx.rst                 |   6 +
 doc/guides/cryptodevs/octeontx2.rst                |   8 +
 doc/guides/cryptodevs/overview.rst                 |   6 +
 doc/guides/rel_notes/release_21_05.rst             |  32 ++
 doc/guides/sample_app_ug/ipsec_secgw.rst           |  15 +-
 doc/guides/tools/cryptoperf.rst                    |   8 +-
 drivers/baseband/acc100/rte_acc100_pmd.c           |  42 +-
 drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c |  10 +-
 drivers/baseband/fpga_lte_fec/fpga_lte_fec.c       |  24 +-
 drivers/baseband/turbo_sw/bbdev_turbo_software.c   |  18 +-
 drivers/common/cpt/cpt_mcode_defines.h             |   7 +-
 drivers/common/cpt/cpt_ucode.h                     |  42 +-
 drivers/common/qat/qat_qp.c                        |   3 +-
 drivers/crypto/octeontx/otx_cryptodev_ops.c        |  15 +-
 drivers/crypto/octeontx2/otx2_cryptodev.c          |   3 +-
 drivers/crypto/octeontx2/otx2_cryptodev_ops.c      |  15 +-
 drivers/crypto/octeontx2/otx2_cryptodev_sec.c      | 145 +++---
 drivers/crypto/octeontx2/otx2_cryptodev_sec.h      |   4 +-
 drivers/crypto/octeontx2/otx2_ipsec_po.h           |   7 +-
 drivers/crypto/octeontx2/otx2_ipsec_po_ops.h       |   8 +-
 drivers/crypto/qat/qat_sym.c                       |  76 ++-
 drivers/crypto/qat/qat_sym.h                       |  66 ++-
 drivers/crypto/qat/qat_sym_hw_dp.c                 |  21 +-
 drivers/crypto/qat/qat_sym_pmd.c                   |   6 +
 drivers/crypto/qat/qat_sym_session.c               |  10 +-
 drivers/crypto/qat/qat_sym_session.h               |   3 +-
 examples/ipsec-secgw/ipsec-secgw.c                 |  49 +-
 examples/ipsec-secgw/ipsec-secgw.h                 |   3 +
 examples/ipsec-secgw/ipsec.c                       |  10 +
 examples/ipsec-secgw/ipsec.h                       |   2 +
 examples/ipsec-secgw/sa.c                          |  18 +
 examples/ipsec-secgw/sad.h                         |   7 +-
 examples/l2fwd-crypto/main.c                       |  40 +-
 lib/librte_bbdev/rte_bbdev_op.h                    |  10 +-
 lib/librte_cryptodev/rte_crypto_sym.h              |  37 +-
 lib/librte_cryptodev/rte_cryptodev.c               |   9 +-
 lib/librte_cryptodev/rte_cryptodev.h               |  26 +
 48 files changed, 1330 insertions(+), 239 deletions(-)

             reply	other threads:[~2021-04-16 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 10:46 Akhil Goyal [this message]
2021-04-16 16:48 ` 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=20210416104625.1743193-1-gakhil@marvell.com \
    --to=gakhil@marvell.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).