From: Volodymyr Fialko <vfialko@marvell.com>
To: <dev@dpdk.org>
Cc: <jerinj@marvell.com>, <gakhil@marvell.com>, <anoobj@marvell.com>,
<abhinandan.gujjar@intel.com>,
Volodymyr Fialko <vfialko@marvell.com>
Subject: [PATCH v3 0/2] Vector support for event crypto adapter
Date: Sat, 1 Oct 2022 02:42:11 +0200 [thread overview]
Message-ID: <20221001004213.2911114-1-vfialko@marvell.com> (raw)
In-Reply-To: <20220926113607.1613674-1-vfialko@marvell.com>
Introduce ability to aggregate crypto operations processed by event
crypto adapter into single event containing rte_event_vector whose event
type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR.
* Changes since v1
- Add missing newline/space issues
- Add missing error messages
- Remove double check of conf input parameter
* Changes since v2
- Rebase on top of dpdk-next-eventdev branch
- Remove already merged patch
Volodymyr Fialko (2):
eventdev: introduce event cryptodev vector type
crypto/cnxk: add vectorization for event crypto
app/test-eventdev/test_perf_common.c | 11 +-
app/test/test_event_crypto_adapter.c | 12 +-
.../prog_guide/event_crypto_adapter.rst | 23 +-
drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 398 ++++++++++++++++--
drivers/crypto/cnxk/cn10k_cryptodev_ops.h | 2 +
drivers/crypto/cnxk/cnxk_cryptodev_ops.h | 9 +-
drivers/crypto/cnxk/version.map | 1 +
drivers/event/cnxk/cn10k_eventdev.c | 33 +-
drivers/event/cnxk/cn10k_worker.h | 6 +-
drivers/event/cnxk/cn9k_eventdev.c | 10 +-
drivers/event/cnxk/cnxk_eventdev.h | 4 +-
drivers/event/cnxk/cnxk_eventdev_adptr.c | 17 +-
drivers/event/dpaa/dpaa_eventdev.c | 9 +-
drivers/event/dpaa2/dpaa2_eventdev.c | 9 +-
drivers/event/octeontx/ssovf_evdev.c | 4 +-
lib/eventdev/eventdev_pmd.h | 35 +-
lib/eventdev/eventdev_trace.h | 6 +-
lib/eventdev/rte_event_crypto_adapter.c | 105 ++++-
lib/eventdev/rte_event_crypto_adapter.h | 101 ++++-
lib/eventdev/rte_eventdev.h | 8 +
20 files changed, 698 insertions(+), 105 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2022-10-01 0:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 1:38 [PATCH v2] app/test: add event inline security tests Volodymyr Fialko
2022-06-22 11:33 ` [PATCH v3] " Volodymyr Fialko
2022-06-22 16:32 ` Anoob Joseph
2022-06-28 8:29 ` Akhil Goyal
2022-06-28 12:09 ` [PATCH] doc: announce change in crypto adapter queue add Volodymyr Fialko
2022-06-28 12:40 ` Akhil Goyal
2022-07-11 14:56 ` Jerin Jacob
2022-07-12 5:31 ` [EXT] " Akhil Goyal
2022-07-13 6:49 ` Gujjar, Abhinandan S
2022-07-14 9:04 ` Hemant Agrawal
2022-07-17 11:32 ` Thomas Monjalon
2022-08-04 9:59 ` [PATCH 0/3] Vector support for event crypto adapter Volodymyr Fialko
2022-08-04 9:59 ` [PATCH 1/3] eventdev: introduce event cryptodev vector type Volodymyr Fialko
2022-09-21 18:32 ` Akhil Goyal
2022-09-22 4:53 ` Gujjar, Abhinandan S
2022-09-24 8:43 ` Gujjar, Abhinandan S
2022-09-26 11:02 ` Volodymyr Fialko
2022-09-27 9:05 ` Gujjar, Abhinandan S
2022-09-27 9:24 ` Volodymyr Fialko
2022-09-27 9:38 ` Gujjar, Abhinandan S
2022-09-27 13:26 ` Jerin Jacob
2022-09-28 14:43 ` Gujjar, Abhinandan S
2022-09-28 16:13 ` Jerin Jacob
2022-08-04 9:59 ` [PATCH 2/3] crypto/cnxk: add burst enqueue for event crypto Volodymyr Fialko
2022-08-04 9:59 ` [PATCH 3/3] crypto/cnxk: add vectorization " Volodymyr Fialko
2022-09-26 11:36 ` [PATCH v2 0/3] Vector support for event crypto adapter Volodymyr Fialko
2022-09-26 11:36 ` [PATCH v2 1/3] eventdev: introduce event cryptodev vector type Volodymyr Fialko
2022-09-26 11:36 ` [PATCH v2 2/3] crypto/cnxk: add burst enqueue for event crypto Volodymyr Fialko
2022-09-26 11:36 ` [PATCH v2 3/3] crypto/cnxk: add vectorization " Volodymyr Fialko
2022-10-01 0:42 ` Volodymyr Fialko [this message]
2022-10-01 0:42 ` [PATCH v3 1/2] eventdev: introduce event cryptodev vector type Volodymyr Fialko
2022-10-01 0:42 ` [PATCH v3 2/2] crypto/cnxk: add vectorization for event crypto Volodymyr Fialko
2022-10-01 3:42 ` [PATCH v3 0/2] Vector support for event crypto adapter Akhil Goyal
2022-10-01 8:00 ` Gujjar, Abhinandan S
2022-10-01 8:47 ` Akhil Goyal
2022-10-02 1:56 ` Gujjar, Abhinandan S
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=20221001004213.2911114-1-vfialko@marvell.com \
--to=vfialko@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.