Add note to cryptodev API that chained mbufs are not supported in DOCSISBPI mode.
Signed-off-by: Fiona Trahe <fiona.tr...@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