Re: [dpdk-dev] crypto drivers in the API

[Thomas Monjalon <thomas.monjalon@6wind.com>]

(resent to fix email address)
2017-02-13 14:25, Thomas Monjalon:
> In the crypto API, the drivers are listed.
> In my opinion, it is a wrong designed and these lists should be removed.
> Do we need a deprecation notice to plan this removal in 17.05, while
> working on bus abstraction?
> 
> 
> lib/librte_cryptodev/rte_cryptodev.h:
> 
> #define CRYPTODEV_NAME_NULL_PMD     crypto_null
> /**< Null crypto PMD device name */
> #define CRYPTODEV_NAME_AESNI_MB_PMD crypto_aesni_mb
> /**< AES-NI Multi buffer PMD device name */
> #define CRYPTODEV_NAME_AESNI_GCM_PMD    crypto_aesni_gcm
> /**< AES-NI GCM PMD device name */
> #define CRYPTODEV_NAME_OPENSSL_PMD  crypto_openssl
> /**< Open SSL Crypto PMD device name */
> #define CRYPTODEV_NAME_QAT_SYM_PMD  crypto_qat
> /**< Intel QAT Symmetric Crypto PMD device name */
> #define CRYPTODEV_NAME_SNOW3G_PMD   crypto_snow3g
> /**< SNOW 3G PMD device name */
> #define CRYPTODEV_NAME_KASUMI_PMD   crypto_kasumi
> /**< KASUMI PMD device name */
> #define CRYPTODEV_NAME_ZUC_PMD      crypto_zuc
> /**< KASUMI PMD device name */
> #define CRYPTODEV_NAME_ARMV8_PMD    crypto_armv8
> /**< ARMv8 Crypto PMD device name */
> #define CRYPTODEV_NAME_SCHEDULER_PMD    crypto_scheduler
> /**< Scheduler Crypto PMD device name */
> 
> /** Crypto device type */
> enum rte_cryptodev_type {
>     RTE_CRYPTODEV_NULL_PMD = 1, /**< Null crypto PMD */
>     RTE_CRYPTODEV_AESNI_GCM_PMD,    /**< AES-NI GCM PMD */
>     RTE_CRYPTODEV_AESNI_MB_PMD, /**< AES-NI multi buffer PMD */
>     RTE_CRYPTODEV_QAT_SYM_PMD,  /**< QAT PMD Symmetric Crypto */
>     RTE_CRYPTODEV_SNOW3G_PMD,   /**< SNOW 3G PMD */
>     RTE_CRYPTODEV_KASUMI_PMD,   /**< KASUMI PMD */
>     RTE_CRYPTODEV_ZUC_PMD,      /**< ZUC PMD */
>     RTE_CRYPTODEV_OPENSSL_PMD,    /**<  OpenSSL PMD */
>     RTE_CRYPTODEV_ARMV8_PMD,    /**< ARMv8 crypto PMD */
>     RTE_CRYPTODEV_SCHEDULER_PMD,    /**< Crypto Scheduler PMD */
> };