From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: fiona.trahe@intel.com, pablo.de.lara.guarch@intel.com,
john.griffin@intel.com, deepak.k.jain@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH 1/3] lib/librte_cryptodev: add private member to crypto op struct
Date: Wed, 30 Nov 2016 15:52:13 +0000 [thread overview]
Message-ID: <1480521135-14869-2-git-send-email-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <1480521135-14869-1-git-send-email-arkadiuszx.kusztal@intel.com>
This commit adds void * _priv member to rte_crypto_op struct to be used
by internal driver operations.
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
lib/librte_cryptodev/rte_crypto.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/librte_cryptodev/rte_crypto.h b/lib/librte_cryptodev/rte_crypto.h
index 9019518..9aa09ce 100644
--- a/lib/librte_cryptodev/rte_crypto.h
+++ b/lib/librte_cryptodev/rte_crypto.h
@@ -117,6 +117,9 @@ struct rte_crypto_op {
struct rte_crypto_sym_op *sym;
/**< Symmetric operation parameters */
}; /**< operation specific parameters */
+
+ void *_priv;
+ /**< Private pointer to be used by driver */
} __rte_cache_aligned;
/**
@@ -146,6 +149,7 @@ __rte_crypto_op_reset(struct rte_crypto_op *op, enum rte_crypto_op_type type)
}
op->opaque_data = NULL;
+ op->_priv = NULL;
}
/**
--
2.1.0
next prev parent reply other threads:[~2016-11-30 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:52 [dpdk-dev] [PATCH 0/3] Add scatter-gather list capability to Intel QuickAssist Technology driver Arek Kusztal
2016-11-30 15:52 ` Arek Kusztal [this message]
2016-11-30 15:52 ` [dpdk-dev] [PATCH 2/3] crypto/qat: add SGL capability to Intel QuickAssist driver Arek Kusztal
2016-11-30 15:52 ` [dpdk-dev] [PATCH 3/3] app/test: add SGL tests to cryptodev QAT suite Arek 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=1480521135-14869-2-git-send-email-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--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).