test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yogesh Jangra <yogesh.jangra@intel.com>
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	[thread overview]
Message-ID: <20230501225842.1163820-5-yogesh.jangra@intel.com> (raw)
In-Reply-To: <20230501225842.1163820-1-yogesh.jangra@intel.com>

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 <yogesh.jangra@intel.com>
Signed-off-by: Harshad Narayane <harshad.suresh.narayane@intel.com>
Signed-off-by: Kamalakannan R <kamalakannan.r@intel.com>
---
 ...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


  parent reply	other threads:[~2023-05-01 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 22:58 [PATCH 0/4] Added testcases for dpdk 23.03 release features Yogesh Jangra
2023-05-01 22:58 ` [PATCH 1/4] dep/pipeline: updated dependencies for mempool parameter Yogesh Jangra
2023-05-01 22:58 ` [PATCH 2/4] dep/pipeline: added dependency for dpdk 23.03 release testcases Yogesh Jangra
2023-05-01 22:58 ` [PATCH 3/4] tests/pipeline: added testcases for dpdk 23.03 release Yogesh Jangra
2023-05-01 22:58 ` Yogesh Jangra [this message]
2023-05-25  2:53   ` [PATCH 4/4] test_plan: updated testsuite details for ipsec testcases lijuan.tu

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=20230501225842.1163820-5-yogesh.jangra@intel.com \
    --to=yogesh.jangra@intel.com \
    --cc=dts@dpdk.org \
    --cc=harshad.suresh.narayane@intel.com \
    --cc=kamalakannan.r@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).