From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: ferruh.yigit@amd.com, kai.ji@intel.com, brian.dooley@intel.com,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v2 0/3] net: add thread-safe crc api
Date: Tue, 1 Oct 2024 19:11:47 +0100 [thread overview]
Message-ID: <20241001181150.43506-1-arkadiuszx.kusztal@intel.com> (raw)
The current net CRC API is not thread-safe, this patch
solves this by adding another, thread-safe API functions.
This API is also safe to use across multiple processes,
yet with limitations on max-simd-bitwidth, which will be checked only by
the process that created the CRC context; all other processes will use
the same CRC function when used with the same CRC context.
It is an undefined behavior when process binaries are compiled
with different SIMD capabilities when the same CRC context is used
v2:
- removed old API
- added multi-process support
- replaced test cases
- marked internal functions as __rte_internal
Arkadiusz Kusztal (3):
net: add thread-safe crc api
crypto/qat: use process safe crc api
test/crc: replace thread-unsafe api functions
app/test/test_crc.c | 168 ++++++++-----------
doc/guides/cryptodevs/qat.rst | 6 +
drivers/crypto/qat/qat_sym.h | 6 +-
drivers/crypto/qat/qat_sym_session.c | 3 +
drivers/crypto/qat/qat_sym_session.h | 2 +
lib/net/net_crc.h | 19 ++-
lib/net/rte_net_crc.c | 309 ++++++++++-------------------------
lib/net/rte_net_crc.h | 40 +----
lib/net/version.map | 18 +-
9 files changed, 204 insertions(+), 367 deletions(-)
--
2.13.6
next reply other threads:[~2024-10-01 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 18:11 Arkadiusz Kusztal [this message]
2024-10-01 18:11 ` [PATCH v2 1/3] " Arkadiusz Kusztal
2024-10-01 21:44 ` Stephen Hemminger
2024-10-01 18:11 ` [PATCH v2 2/3] crypto/qat: use process safe " Arkadiusz Kusztal
2024-10-01 18:11 ` [PATCH v2 3/3] test/crc: replace thread-unsafe api functions Arkadiusz Kusztal
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=20241001181150.43506-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=kai.ji@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).