From: Samina Arshad <samina.arshad@intel.com>
To: dts@dpdk.org
Cc: ciara.power@intel.com, Samina Arshad <samina.arshad@intel.com>
Subject: [PATCH v1] test_plans/fips: modified prerequisites
Date: Thu, 15 Jun 2023 12:32:48 +0000 [thread overview]
Message-ID: <20230615123248.40551-1-samina.arshad@intel.com> (raw)
Added in up-to-date installation steps for aesni_mb and
QAT by adding in up-to-date DPDK documentation links, in
order to allow the user to use correct version of tools
needed.
Signed-off-by: Samina Arshad <samina.arshad@intel.com>
---
test_plans/fips_cryptodev_test_plan.rst | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/test_plans/fips_cryptodev_test_plan.rst b/test_plans/fips_cryptodev_test_plan.rst
index fcbb8286..f43dd4f8 100644
--- a/test_plans/fips_cryptodev_test_plan.rst
+++ b/test_plans/fips_cryptodev_test_plan.rst
@@ -21,17 +21,13 @@ Limitations and Supported test vectors, please see http://doc.dpdk.org/guides/sa
Prerequisites
=============
-Get the latest IPSec Multi-buffer library (nasm package is required, for Ubuntu "apt install nasm", for Fedora/RHEL "dnf install nasm")::
+For AESNI_MB SW PMD tests, find the latest dependency installation steps (such as IPSec Multi-buffer library) in the DPDK documentation::
- git clone https://github.com/intel/intel-ipsec-mb.git
+ https://doc.dpdk.org/guides/cryptodevs/aesni_mb.html
- cd intel-ipsec-mb
+For the tests requiring QAT, find the installation steps in the DPDK documentation::
- git checkout d3e25eed9d010b2c24b9970828eb9b45f4795c06 (latest working commit)
-
- make -j 4
-
- make install
+ https://doc.dpdk.org/guides/cryptodevs/qat.html
Get/install FIPS Object Module::
--
2.25.1
next reply other threads:[~2023-06-15 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:32 Samina Arshad [this message]
2023-06-19 10:22 ` Power, Ciara
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=20230615123248.40551-1-samina.arshad@intel.com \
--to=samina.arshad@intel.com \
--cc=ciara.power@intel.com \
--cc=dts@dpdk.org \
/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).