From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EC69E42A34; Mon, 1 May 2023 21:07:44 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E8EE841153; Mon, 1 May 2023 21:07:44 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id AA1C74021E for ; Mon, 1 May 2023 21:07:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1682968063; x=1714504063; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=K10aJduWIeUu5gIrQAPtdJaAHZG1gD1tF16r6jkuKVY=; b=ZY06oDRMPI17z3otY1zEalSYGWIcthQ0pAmQw1MWqIcYWOT0hlVCSdPb 5fgcTBf/p5ttUUKOELA/QKnDaLSVzHIfCxNe7+gZ5B28/jBMCFrh+Lokv Wel+nzTtyI1Nqh0NIojdYJ0mwiJ7h67kPApmHjMxmYwzQ7U6qvpJLeOM6 l3+v+PFcPBtoyi6FtxjMQq+NVfNc5d7msjFQwpZ+xMWgQvBRhVeoI4yvd NSP+2kz1XPE60WPPbcvwzogHW7itqNVfaJGf++ofW/in4lvwbAfzefTor GzV38rV1Dm+szVIbfvY7qQk0V/w75DKRR7t48WyAlXemMBSfPNNP3jzYR A==; X-IronPort-AV: E=McAfee;i="6600,9927,10697"; a="347026209" X-IronPort-AV: E=Sophos;i="5.99,242,1677571200"; d="scan'208";a="347026209" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 May 2023 12:07:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10697"; a="728641154" X-IronPort-AV: E=Sophos;i="5.99,242,1677571200"; d="scan'208";a="728641154" Received: from ena4.iind.intel.com (HELO localhost.localdomain) ([10.190.200.224]) by orsmga001.jf.intel.com with ESMTP; 01 May 2023 12:07:41 -0700 From: Yogesh Jangra To: dts@dpdk.org Cc: kamalakannan.r@intel.com, harshad.suresh.narayane@intel.com Subject: [PATCH 4/4] test_plan: updated testsuite details for ipsec testcases Date: Mon, 1 May 2023 18:58:42 -0400 Message-Id: <20230501225842.1163820-5-yogesh.jangra@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230501225842.1163820-1-yogesh.jangra@intel.com> References: <20230501225842.1163820-1-yogesh.jangra@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org IPSEC feature requires installation of librarires. Added the details related to the required libraries, along with sample script that can be used to install the libraries. Signed-off-by: Yogesh Jangra Signed-off-by: Harshad Narayane Signed-off-by: Kamalakannan R --- ...mple_crypto_devices_installation_script.sh | 53 +++++++++++++++++++ test_plans/pipeline_test_plan.rst | 7 +++ 2 files changed, 60 insertions(+) create mode 100644 dep/pipeline/sample_crypto_devices_installation_script.sh diff --git a/dep/pipeline/sample_crypto_devices_installation_script.sh b/dep/pipeline/sample_crypto_devices_installation_script.sh new file mode 100644 index 00000000..e1f23127 --- /dev/null +++ b/dep/pipeline/sample_crypto_devices_installation_script.sh @@ -0,0 +1,53 @@ +#SPDX-License-Identifier: BSD-3-Clause +#Copyright(c) 2023 Intel Corporation + +#!/usr/bin/env bash +#set -o xtrace + +NASM_VERSION=2.15.05 +NASM_TAR_FILE=nasm-$NASM_VERSION.tar.gz +NASM_DIR=nasm-$NASM_VERSION +NASM_INSTALLATION_LINK=https://www.nasm.us/pub/nasm/releasebuilds/$NASM_VERSION/$NASM_TAR_FILE +IPSEC_AESNI_MB_BRANCH_TAG=v1.2 +INSTALLATION_PATH=~ + +#Switching to installation directory path +echo "Switching to installation directory path: $INSTALLATION_PATH." +cd $INSTALLATION_PATH + +if [ -d "$INSTALLATION_PATH/crypto_devices" ] +then + #Removing previously created crypto device directory + echo "Removing crypto directories at the $INSTALLATION_PATH path." + rm -rf crypto_devices +fi + +#Creating crypto device directory at installation path +echo "Creating installation directory at $INSTALLATION_PATH." +mkdir crypto_devices + +#Switching to crypto device directory +echo "Switching to installation directory."I +cd crypto_devices +echo "Switched to installation directory." + +#Installing NASM +echo "Installing NASM...." +wget $NASM_INSTALLATION_LINK +tar -xvf $NASM_TAR_FILE +cd $NASM_DIR +./configure +make +sudo make install +echo "NASM installed successfully." + +#Installing IPSEC_AESNI_MB +#Switching back to installation directory +cd ../ +echo "Installing IPSEC_AESNI_MB...." +git clone https://github.com/intel/intel-ipsec-mb.git +cd intel-ipsec-mb/ +git checkout tags/$IPSEC_AESNI_MB_BRANCH_TAG +make +sudo make install +echo "IPSEC_AESNI_MB installed successfully." \ No newline at end of file diff --git a/test_plans/pipeline_test_plan.rst b/test_plans/pipeline_test_plan.rst index ee7a2af5..c887cadc 100644 --- a/test_plans/pipeline_test_plan.rst +++ b/test_plans/pipeline_test_plan.rst @@ -36,6 +36,13 @@ Supporting Files All the supporting files for this test suite are maintained in the folder named "pipeline" present in the {DTS_SRC_DIR}/dep directory. +Crypto device library installation is prerequisite to run/execute ipsec testcases. +The testcases added in the testsuite uses "Intel(R) Multi-Buffer Crypto for +IPsec Library (AESNI MB PMD)" as a crypto device for encryption and decryption. +Installation of crypto device library must be done before executing ipsec testcases +for successful execution. A sample script for the installation of the crypto device +(here, AESNI MB) has been provided at {DTS_SRC_DIR}/dep/pipeline/} directory. + Directory Structure of Each Test Case ===================================== Within {DTS_SRC_DIR}/dep/pipeline folder, all files related to a particular test case are maintained -- 2.25.1