DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] next-eventdev 21.05-rc1
Date: Sat, 17 Apr 2021 17:28:52 +0000	[thread overview]
Message-ID: <SN7PR18MB439810C5C731FAA4A2C72D9AC84B9@SN7PR18MB4398.namprd18.prod.outlook.com> (raw)

The following changes since commit 74299cc7591192cbc72e8f411dff0c7f3cfdf309:

  buildtools: fix all drivers disabled on Windows (2021-04-17 12:49:23 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 6e5aa8854846c884885391ddc84b2629de198e68:

  eventdev: fix case to initiate crypto adapter service (2021-04-17 22:52:41 +0530)

----------------------------------------------------------------
Akhil Goyal (1):
      eventdev: introduce crypto adapter enqueue API

Shijith Thotton (3):
      event/octeontx2: support crypto adapter forward mode
      test/event_crypto: use crypto adapter enqueue API
      eventdev: fix case to initiate crypto adapter service

 app/test/test_event_crypto_adapter.c               | 33 +++++----
 devtools/libabigail.abignore                       |  5 ++
 doc/guides/prog_guide/event_crypto_adapter.rst     | 69 +++++++++++-------
 doc/guides/rel_notes/release_21_05.rst             |  7 ++
 drivers/crypto/octeontx2/otx2_cryptodev_ops.c      | 49 +++++++++----
 drivers/event/octeontx2/otx2_evdev.c               |  5 +-
 drivers/event/octeontx2/otx2_evdev_crypto_adptr.c  |  3 +-
 ...pto_adptr_dp.h => otx2_evdev_crypto_adptr_rx.h} |  6 +-
 .../event/octeontx2/otx2_evdev_crypto_adptr_tx.h   | 83 ++++++++++++++++++++++
 drivers/event/octeontx2/otx2_worker.h              |  2 +-
 drivers/event/octeontx2/otx2_worker_dual.h         |  2 +-
 lib/librte_eventdev/eventdev_trace_points.c        |  3 +
 lib/librte_eventdev/rte_event_crypto_adapter.c     |  1 +
 lib/librte_eventdev/rte_event_crypto_adapter.h     | 63 ++++++++++++++++
 lib/librte_eventdev/rte_eventdev.c                 | 10 +++
 lib/librte_eventdev/rte_eventdev.h                 |  9 ++-
 lib/librte_eventdev/rte_eventdev_trace_fp.h        | 10 +++
 lib/librte_eventdev/version.map                    |  1 +
 18 files changed, 301 insertions(+), 60 deletions(-)
 rename drivers/event/octeontx2/{otx2_evdev_crypto_adptr_dp.h => otx2_evdev_crypto_adptr_rx.h} (93%)
 create mode 100644 drivers/event/octeontx2/otx2_evdev_crypto_adptr_tx.h

             reply	other threads:[~2021-04-17 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 17:28 Jerin Jacob Kollanukkaran [this message]
2021-04-18 23:33 ` 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=SN7PR18MB439810C5C731FAA4A2C72D9AC84B9@SN7PR18MB4398.namprd18.prod.outlook.com \
    --to=jerinj@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).