From: Radu Nicolau <radu.nicolau@intel.com>
To: dev@dpdk.org
Cc: kai.ji@intel.com, Radu Nicolau <radu.nicolau@intel.com>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Subject: [RFC] lib/cryptodev: update API documentation for aux_flags
Date: Wed, 27 Aug 2025 09:43:37 +0000 [thread overview]
Message-ID: <20250827094338.767062-1-radu.nicolau@intel.com> (raw)
Update the API documentation description of rte_crypto_op field
aux_flags as to allow PMDs to define driver-specific flags.
Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
---
lib/cryptodev/rte_crypto.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/cryptodev/rte_crypto.h b/lib/cryptodev/rte_crypto.h
index dcf4a36fb2..38c8acbf4c 100644
--- a/lib/cryptodev/rte_crypto.h
+++ b/lib/cryptodev/rte_crypto.h
@@ -116,6 +116,10 @@ struct rte_crypto_op {
* the status is RTE_CRYPTO_OP_STATUS_SUCCESS.
* In case of errors, the value of this field is undefined.
*
+ * In addition to RTE_CRYPTO_OP_AUX_FLAGS_* the PMDs can define
+ * their own optional auxiliary flags as needed, set by the
+ * application and to be used for driver-specific purposes.
+ *
* With TLS record offload (RTE_SECURITY_PROTOCOL_TLS_RECORD),
* application may provide the extra padding required for the plaintext
* provided. This field can be used for passing the same in units of 8B.
--
2.50.1
reply other threads:[~2025-08-27 9:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250827094338.767062-1-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.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).