From: Fiona Trahe <fiona.trahe@intel.com>
To: dev@dpdk.org, pablo.de.lara.guarch@intel.com
Cc: fiona.trahe@intel.com
Subject: [dpdk-dev] [PATCH] cryptodev: add API note
Date: Thu, 23 Mar 2017 17:36:10 +0000 [thread overview]
Message-ID: <1490290570-14651-1-git-send-email-fiona.trahe@intel.com> (raw)
Add note to cryptodev API that chained mbufs
are not supported in DOCSISBPI mode.
Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
---
lib/librte_cryptodev/rte_crypto_sym.h | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/lib/librte_cryptodev/rte_crypto_sym.h b/lib/librte_cryptodev/rte_crypto_sym.h
index 4d5459f..e066b0a 100644
--- a/lib/librte_cryptodev/rte_crypto_sym.h
+++ b/lib/librte_cryptodev/rte_crypto_sym.h
@@ -417,8 +417,20 @@ struct rte_cryptodev_sym_session;
* to the data in the source buffer.
*/
struct rte_crypto_sym_op {
- struct rte_mbuf *m_src; /**< source mbuf */
- struct rte_mbuf *m_dst; /**< destination mbuf */
+ struct rte_mbuf *m_src;
+ /**< source mbuf
+ *
+ * @note
+ * For DOCSISBPI mode rte_mbuf.next must be NULL, i.e.
+ * chained mbufs are not supported in this mode.
+ */
+ struct rte_mbuf *m_dst;
+ /**< destination mbuf
+ *
+ * @note
+ * For DOCSISBPI mode rte_mbuf.next must be NULL, i.e.
+ * chained mbufs are not supported in this mode.
+ */
enum rte_crypto_sym_op_sess_type sess_type;
--
2.5.0
next reply other threads:[~2017-03-23 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 17:36 Fiona Trahe [this message]
2017-03-24 10:52 ` Declan Doherty
2017-03-24 12:52 ` Trahe, Fiona
2017-03-30 13:51 ` Declan Doherty
2017-04-03 15:51 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2017-04-04 9:07 ` Declan Doherty
2017-04-04 9:48 ` De Lara Guarch, Pablo
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=1490290570-14651-1-git-send-email-fiona.trahe@intel.com \
--to=fiona.trahe@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).