From: David Coyle <david.coyle@intel.com>
To: dev@dpdk.org
Cc: kai.ji@intel.com, anoobj@marvell.com, jerinj@marvell.com,
ciara.power@intel.com, kevin.osullivan@intel.com,
David Coyle <david.coyle@intel.com>
Subject: [PATCH v4 0/2] crypto/scheduler: add support for DOCSIS security protocol
Date: Tue, 19 Sep 2023 14:14:38 +0000 [thread overview]
Message-ID: <20230919141440.39305-1-david.coyle@intel.com> (raw)
In-Reply-To: <20230914152207.19794-1-david.coyle@intel.com>
This patchset adds support to the cryptodev scheduler PMD and unit
tests for the DOCSIS security protocol. Support for other stateless
security protocols can be added in the future as required with relative
ease now that the framework is in place.
v4:
* Address review comments from Anoob
* Remove unnecessary pointer type casting
* Free capability and worker name memory if memory allocation fails
during scheduler PMD creation
* Use RTE_MAX when getting max worker session size
v3:
* Limit support to the DOCSIS security protocol only
v2:
* Improve inclusion of rte_security header files
* Fix typo in commit message
Series-acked-by: Ciara Power <ciara.power@intel.com>
David Coyle (2):
crypto/scheduler: support DOCSIS security protocol
test/crypto: add DOCSIS security tests for cryptodev scheduler
app/test/test_cryptodev.c | 12 +-
doc/guides/rel_notes/release_23_11.rst | 4 +
drivers/crypto/scheduler/meson.build | 2 +-
.../scheduler/rte_cryptodev_scheduler.c | 218 ++++++++++-
drivers/crypto/scheduler/scheduler_failover.c | 12 +-
.../crypto/scheduler/scheduler_multicore.c | 10 +-
.../scheduler/scheduler_pkt_size_distr.c | 54 +--
drivers/crypto/scheduler/scheduler_pmd.c | 59 ++-
drivers/crypto/scheduler/scheduler_pmd_ops.c | 370 +++++++++++++-----
.../crypto/scheduler/scheduler_pmd_private.h | 155 +++++---
.../crypto/scheduler/scheduler_roundrobin.c | 6 +-
11 files changed, 668 insertions(+), 234 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2023-09-19 14:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:14 [PATCH 0/2] crypto/scheduler: add support for security protocols David Coyle
2023-08-09 10:14 ` [PATCH 1/2] crypto/scheduler: support " David Coyle
2023-08-09 10:14 ` [PATCH 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 10:23 ` [PATCH v2 0/2] crypto/scheduler: add support for security protocols David Coyle
2023-08-11 10:24 ` [PATCH v2 1/2] crypto/scheduler: support " David Coyle
2023-08-11 10:24 ` [PATCH v2 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 11:09 ` [EXT] [PATCH v2 0/2] crypto/scheduler: add support for security protocols Anoob Joseph
2023-09-11 16:02 ` Coyle, David
2023-09-13 7:02 ` Anoob Joseph
2023-09-14 15:22 ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol David Coyle
2023-09-14 15:22 ` [PATCH v3 1/2] crypto/scheduler: support " David Coyle
2023-09-18 11:02 ` [EXT] " Anoob Joseph
2023-09-19 14:16 ` Coyle, David
2023-09-14 15:22 ` [PATCH v3 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-15 10:18 ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol Power, Ciara
2023-09-15 14:02 ` Power, Ciara
2023-09-19 14:14 ` David Coyle [this message]
2023-09-19 14:14 ` [PATCH v4 1/2] crypto/scheduler: support " David Coyle
2023-09-19 14:14 ` [PATCH v4 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-20 5:45 ` [EXT] [PATCH v4 0/2] crypto/scheduler: add support for DOCSIS security protocol Anoob Joseph
2023-09-21 7:18 ` Akhil Goyal
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=20230919141440.39305-1-david.coyle@intel.com \
--to=david.coyle@intel.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@intel.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 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).