From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akhil Goyal Subject: Re: [PATCH v3 09/16] cryptodev: remove max number of sessions parameter Date: Wed, 4 Jul 2018 18:12:23 +0530 Message-ID: <74b68fb7-9618-93a9-2dd1-c0963290633a@nxp.com> References: <20180608220234.10170-1-pablo.de.lara.guarch@intel.com> <20180628005304.26544-1-pablo.de.lara.guarch@intel.com> <20180628005304.26544-10-pablo.de.lara.guarch@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Pablo de Lara , declan.doherty@intel.com, shally.verma@caviumnetworks.com, ravi1.kumar@amd.com, jerin.jacob@caviumnetworks.com, roy.fan.zhang@intel.com, fiona.trahe@intel.com, tdu@semihalf.com, jianjay.zhou@huawei.com Return-path: Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50070.outbound.protection.outlook.com [40.107.5.70]) by dpdk.org (Postfix) with ESMTP id 3421B1BEF8 for ; Wed, 4 Jul 2018 14:42:39 +0200 (CEST) In-Reply-To: <20180628005304.26544-10-pablo.de.lara.guarch@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Pablo, On 6/28/2018 6:22 AM, Pablo de Lara wrote: > Most crypto PMDs do not have a limitation > of the number of the sessions that can be handled > internally. The value that was set before was not > actually used at all, since the sessions are created > at the application level. > Therefore, this value is not parsed from the initial > crypto parameters anymore and it is set to 0, > meaning that there is no actual limit. > > Signed-off-by: Pablo de Lara > --- > doc/guides/prog_guide/cryptodev_lib.rst | 5 ++--- > drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 5 +---- > drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c | 3 ++- > drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h | 2 -- > drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 5 +---- > drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 3 ++- > drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 2 -- > drivers/crypto/armv8/rte_armv8_pmd.c | 5 +---- > drivers/crypto/armv8/rte_armv8_pmd_ops.c | 3 ++- > drivers/crypto/armv8/rte_armv8_pmd_private.h | 2 -- > drivers/crypto/ccp/ccp_pmd_ops.c | 3 ++- > drivers/crypto/ccp/ccp_pmd_private.h | 1 - > drivers/crypto/ccp/rte_ccp_pmd.c | 16 +--------------- > drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 4 ++-- > drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 2 -- > drivers/crypto/kasumi/rte_kasumi_pmd.c | 5 +---- > drivers/crypto/kasumi/rte_kasumi_pmd_ops.c | 3 ++- > drivers/crypto/kasumi/rte_kasumi_pmd_private.h | 2 -- > drivers/crypto/mvsam/rte_mrvl_pmd_ops.c | 3 ++- > drivers/crypto/null/null_crypto_pmd.c | 5 +---- > drivers/crypto/null/null_crypto_pmd_ops.c | 3 ++- > drivers/crypto/null/null_crypto_pmd_private.h | 1 - > drivers/crypto/openssl/rte_openssl_pmd.c | 5 +---- > drivers/crypto/openssl/rte_openssl_pmd_ops.c | 3 ++- > drivers/crypto/openssl/rte_openssl_pmd_private.h | 2 -- > drivers/crypto/qat/qat_sym_pmd.c | 6 +++--- > drivers/crypto/qat/qat_sym_pmd.h | 1 - > drivers/crypto/scheduler/scheduler_pmd.c | 13 +------------ > drivers/crypto/scheduler/scheduler_pmd_ops.c | 14 +++++++------- > drivers/crypto/snow3g/rte_snow3g_pmd.c | 5 +---- > drivers/crypto/snow3g/rte_snow3g_pmd_ops.c | 3 ++- > drivers/crypto/snow3g/rte_snow3g_pmd_private.h | 2 -- > drivers/crypto/virtio/virtio_cryptodev.c | 7 +++---- > drivers/crypto/zuc/rte_zuc_pmd.c | 5 +---- > drivers/crypto/zuc/rte_zuc_pmd_ops.c | 3 ++- > drivers/crypto/zuc/rte_zuc_pmd_private.h | 2 -- > lib/librte_cryptodev/rte_cryptodev_pmd.c | 12 ++---------- > lib/librte_cryptodev/rte_cryptodev_pmd.h | 4 ---- > 38 files changed, 49 insertions(+), 121 deletions(-) Relevant Defines in config should also be removed.