From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-eventdev 18.05 RC3
Date: Wed, 9 May 2018 16:28:25 +0530 [thread overview]
Message-ID: <20180509105818.GA4729@jerin> (raw)
The following changes since commit 0256386dc43ce0f27f4c9d6bfa58c534aaf997e2:
mem: add argument to memory event callback (2018-05-08 22:28:58 +0200)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to db3d585ff859251586f24f2bf60ffc276da01cda:
event/dpaa2: remove usage of link under evq info structure (2018-05-09 16:19:05 +0530)
----------------------------------------------------------------
Abhinandan Gujjar (5):
eventdev: introduce event crypto adapter
eventdev: add APIs and PMD callbacks for crypto adapter
eventdev: add crypto adapter implementation
test: add event crypto adapter auto-test
doc: add event crypto adapter documentation
Ashish Jain (1):
event/dpaa2: remove usage of link under evq info structure
Erik Gabriel Carrillo (1):
test: fix build with GCC 4.8.5
Nikhil Rao (1):
eventdev: convert eth Rx adapter files to SPDX license tag
Nipun Gupta (1):
event/dpaa2: remove check on return value from epoll wait
Pavan Nikhilesh (4):
event/octeontx: fix clang 6 linker error
doc: update release notes for OcteonTx TIM driver
event/octeontx: fix incorrect SPDX placement
driver/octeontx: disable PMD for buggy compilers
MAINTAINERS | 7 +
config/common_base | 1 +
config/rte_config.h | 1 +
doc/api/doxy-api-index.md | 1 +
doc/guides/prog_guide/event_crypto_adapter.rst | 296 +++++
.../img/event_crypto_adapter_op_forward.svg | 1078 +++++++++++++++++++
.../prog_guide/img/event_crypto_adapter_op_new.svg | 1061 ++++++++++++++++++
doc/guides/prog_guide/index.rst | 1 +
doc/guides/rel_notes/release_18_05.rst | 13 +
drivers/event/dpaa2/dpaa2_eventdev.c | 21 +-
drivers/event/dpaa2/dpaa2_eventdev.h | 1 -
drivers/event/octeontx/timvf_evdev.c | 3 +-
drivers/event/octeontx/timvf_evdev.h | 5 +-
drivers/event/octeontx/timvf_worker.c | 3 +-
drivers/event/sw/sw_evdev.c | 13 +
lib/Makefile | 3 +-
lib/librte_eventdev/Makefile | 3 +
lib/librte_eventdev/meson.build | 8 +-
lib/librte_eventdev/rte_event_crypto_adapter.c | 1128 ++++++++++++++++++++
lib/librte_eventdev/rte_event_crypto_adapter.h | 575 ++++++++++
lib/librte_eventdev/rte_event_eth_rx_adapter.c | 4 +
lib/librte_eventdev/rte_event_eth_rx_adapter.h | 32 +-
lib/librte_eventdev/rte_eventdev.c | 25 +
lib/librte_eventdev/rte_eventdev.h | 53 +-
lib/librte_eventdev/rte_eventdev_pmd.h | 187 ++++
lib/librte_eventdev/rte_eventdev_version.map | 13 +
mk/toolchain/gcc/rte.toolchain-compat.mk | 8 +
test/test/Makefile | 3 +
test/test/test_event_crypto_adapter.c | 927 ++++++++++++++++
29 files changed, 5412 insertions(+), 62 deletions(-)
create mode 100644 doc/guides/prog_guide/event_crypto_adapter.rst
create mode 100644 doc/guides/prog_guide/img/event_crypto_adapter_op_forward.svg
create mode 100644 doc/guides/prog_guide/img/event_crypto_adapter_op_new.svg
create mode 100644 lib/librte_eventdev/rte_event_crypto_adapter.c
create mode 100644 lib/librte_eventdev/rte_event_crypto_adapter.h
create mode 100644 test/test/test_event_crypto_adapter.c
next reply other threads:[~2018-05-09 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 10:58 Jerin Jacob [this message]
2018-05-09 23:30 ` 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=20180509105818.GA4729@jerin \
--to=jerin.jacob@caviumnetworks.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).