From: xuyanjie <yanjie.xu@intel.com>
To: dts@dpdk.org
Cc: xuyanjie <yanjie.xu@intel.com>
Subject: [dts] [PATCH] add new ipsec lib test scripts
Date: Wed, 17 Apr 2019 05:49:49 -0400 [thread overview]
Message-ID: <1555494589-170504-1-git-send-email-yanjie.xu@intel.com> (raw)
Signed-off-by: xuyanjie <yanjie.xu@intel.com>
diff --git a/tests/TestSuite_cryptodev_new_ipsec-gw.py b/tests/TestSuite_cryptodev_new_ipsec-gw.py
index 5e348db..8062c4f 100644
--- a/tests/TestSuite_cryptodev_new_ipsec-gw.py
+++ b/tests/TestSuite_cryptodev_new_ipsec-gw.py
@@ -66,14 +66,14 @@ class TestIPsecGW(TestCase):
self.logger.info("dut ports = " + str(self.dut_ports))
self.logger.info("ports_socket = " + str(self.ports_socket))
- # Generally, testbed should has 4 ports NIC, like,
+ # Generally, testbed should have 4 ports NIC, like,
# 03:00.0 03:00.1 03:00.2 03:00.3
# This test case will
# - physical link is 03:00.0 <-> 03:00.1 and 03:00.2 <-> 03:00.3
# - bind 03:00.0 and 03:00.2 to ipsec-secgw app
# - send test packet from 03:00.3
# - receive packet which forwarded by ipsec-secgw from 03:00.0
- # - configure port and peer in dts port.cfg
+ # - http://git.dpdk.org/tools/dts/tree/conf/ports.cfg
self.tx_port = self.tester.get_local_port(self.dut_ports[1])
self.rx_port = self.tester.get_local_port(self.dut_ports[0])
@@ -92,7 +92,7 @@ class TestIPsecGW(TestCase):
"config": None,
"P": "",
"p": "0x3",
- "f": "local_conf/ipsec_test.cfg",
+ "f": "conf/new_lib_ipsec_test.cfg",
"u": "0x1"
}
@@ -180,7 +180,7 @@ class TestIPsecGW(TestCase):
result = self._execute_ipsec_gw_test(ipsec_gw_opt_str)
self.verify(result, "FAIL")
- def test_qat_aes_128_ctr_ipv4_transport(self):
+ def test_trs_qat_aes_128_ctr_ipv4(self):
if cc.is_test_skip(self):
return
--
2.7.4
next reply other threads:[~2019-04-17 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 9:49 xuyanjie [this message]
2019-04-23 21:16 ` Tu, Lijuan
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 16:23 xuyanjie
2019-04-16 20:01 ` Rami Rosen
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=1555494589-170504-1-git-send-email-yanjie.xu@intel.com \
--to=yanjie.xu@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).