From: Xinfeng Zhao <xinfengx.zhao@intel.com>
To: dts@dpdk.org
Cc: Xinfeng Zhao <xinfengx.zhao@intel.com>
Subject: [dts] [PATCH V1 3/3] conf: modify the cryptodev conf and specify the qat crypto device
Date: Thu, 6 Jun 2019 08:23:05 +0800 [thread overview]
Message-ID: <1559780585-160319-3-git-send-email-xinfengx.zhao@intel.com> (raw)
In-Reply-To: <1559780585-160319-1-git-send-email-xinfengx.zhao@intel.com>
Signed-off-by: Xinfeng Zhao <xinfengx.zhao@intel.com>
---
conf/l2fwd_cryptodev_func.cfg | 3 +++
conf/unit_tests_cryptodev_func.cfg | 5 ++++-
conf/virtio_ipsec_cryptodev_func.cfg | 1 +
conf/virtio_perf_cryptodev_func.cfg | 1 +
conf/virtio_unit_cryptodev_func.cfg | 1 +
5 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/conf/l2fwd_cryptodev_func.cfg b/conf/l2fwd_cryptodev_func.cfg
index 6f3b146..a1b2418 100644
--- a/conf/l2fwd_cryptodev_func.cfg
+++ b/conf/l2fwd_cryptodev_func.cfg
@@ -7,6 +7,9 @@ l="9,10,66"
socket-mem="2048,0"
n=4
+# specify the qat devices in eal white list
+w="0000:1a:01.0 -w 0000:1c:01.0 -w 0000:1e:01.0"
+
[test_scheduler_rr_AES_CBC_auto]
vdev="crypto_scheduler_pmd_1,slave=0000:1a:01.0_qat_sym,slave=0000:3f:01.0_qat_sym,slave=0000:3d:01.0_qat_sym,mode=round-robin"
diff --git a/conf/unit_tests_cryptodev_func.cfg b/conf/unit_tests_cryptodev_func.cfg
index 9b80025..d5b3b30 100644
--- a/conf/unit_tests_cryptodev_func.cfg
+++ b/conf/unit_tests_cryptodev_func.cfg
@@ -5,4 +5,7 @@ crypto_dev_id="37c9"
# eal config
l="9,10,66"
socket-mem="2048,0 --legacy-mem"
-n=6
\ No newline at end of file
+n=4
+
+# specify the qat device in eal white list to avoid reach the maximum number of crypto devices
+w="0000:1a:01.0"
diff --git a/conf/virtio_ipsec_cryptodev_func.cfg b/conf/virtio_ipsec_cryptodev_func.cfg
index 2e727c6..0b51b7d 100644
--- a/conf/virtio_ipsec_cryptodev_func.cfg
+++ b/conf/virtio_ipsec_cryptodev_func.cfg
@@ -6,6 +6,7 @@ crypto_dev_id="37c9"
vfio_pci="0000:60:00.0 0000:60:00.1 0000:3b:00.0 0000:3b:00.1"
# default crypto device and sw device config
+w="0000:1a:01.0"
vdev="crypto_aesni_mb_pmd_1 --vdev crypto_aesni_mb_pmd_2"
[vm0]
diff --git a/conf/virtio_perf_cryptodev_func.cfg b/conf/virtio_perf_cryptodev_func.cfg
index 5a9b2cb..cdadf31 100644
--- a/conf/virtio_perf_cryptodev_func.cfg
+++ b/conf/virtio_perf_cryptodev_func.cfg
@@ -6,6 +6,7 @@ crypto_dev_id="37c9"
vfio_pci="0000:60:00.0 0000:60:00.1"
# Vhost-crypto option config
+w="0000:1a:01.0"
vdev="crypto_aesni_mb_pmd_1"
[test_aesni_mb_aes_cbc_sha1_hmac]
diff --git a/conf/virtio_unit_cryptodev_func.cfg b/conf/virtio_unit_cryptodev_func.cfg
index 1ffd418..f8165bd 100644
--- a/conf/virtio_unit_cryptodev_func.cfg
+++ b/conf/virtio_unit_cryptodev_func.cfg
@@ -6,6 +6,7 @@ crypto_dev_id="37c9"
vfio_pci="0000:60:00.0 0000:60:00.1"
# Vhost-crypto option config
+w="0000:1a:01.0"
vdev="crypto_aesni_mb_pmd_1"
[vm0]
--
2.7.4
next prev parent reply other threads:[~2019-06-06 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 0:23 [dts] [PATCH V1 1/3] tests: add new case in cryptodev unit-test Xinfeng Zhao
2019-06-06 0:23 ` [dts] [PATCH V1 2/3] tests: modify cryptodev suites to avoid Reaching the maximum number of crypto devices Xinfeng Zhao
2019-06-06 0:23 ` Xinfeng Zhao [this message]
2019-06-11 7:10 ` [dts] [PATCH V1 1/3] tests: add new case in cryptodev unit-test Zhao, XinfengX
2019-06-12 6:31 ` Tu, Lijuan
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=1559780585-160319-3-git-send-email-xinfengx.zhao@intel.com \
--to=xinfengx.zhao@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).