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 DES CBC cipher algorithm
Date: Fri, 2 Dec 2016 14:16:00 +0000 [thread overview]
Message-ID: <1480688162-27474-2-git-send-email-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <1480688162-27474-1-git-send-email-arkadiuszx.kusztal@intel.com>
This commit adds DES CBC ciper algorithm to available algorithms
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
lib/librte_cryptodev/rte_crypto_sym.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/librte_cryptodev/rte_crypto_sym.h b/lib/librte_cryptodev/rte_crypto_sym.h
index d694723..0e20b30 100644
--- a/lib/librte_cryptodev/rte_crypto_sym.h
+++ b/lib/librte_cryptodev/rte_crypto_sym.h
@@ -105,7 +105,11 @@ enum rte_crypto_cipher_algorithm {
RTE_CRYPTO_CIPHER_ZUC_EEA3,
/**< ZUC algorithm in EEA3 mode */
+ RTE_CRYPTO_CIPHER_DES_CBC,
+ /**< DES algorithm in CBC mode */
+
RTE_CRYPTO_CIPHER_LIST_END
+
};
/** Symmetric Cipher Direction */
--
2.1.0
next prev parent reply other threads:[~2016-12-02 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 14:15 [dpdk-dev] [PATCH 0/3] Add DES capability to Intel QuickAssist Technology driver Arek Kusztal
2016-12-02 14:16 ` Arek Kusztal [this message]
2016-12-21 11:49 ` [dpdk-dev] [PATCH 1/3] lib/librte_cryptodev: add DES CBC cipher algorithm Trahe, Fiona
2016-12-02 14:16 ` [dpdk-dev] [PATCH 2/3] crypto/qat: add DES capability to Intel QAT driver Arek Kusztal
2016-12-21 11:49 ` Trahe, Fiona
2016-12-02 14:16 ` [dpdk-dev] [PATCH 3/3] app/test: add DES tests to Intel QAT crypto test suite Arek Kusztal
2016-12-21 11:49 ` Trahe, Fiona
2016-12-21 11:47 ` [dpdk-dev] [PATCH 0/3] Add DES capability to Intel QuickAssist Technology driver Trahe, Fiona
2016-12-21 23:02 ` 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=1480688162-27474-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).