From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Huang, ZhiminX" <zhiminx.huang@intel.com>
Subject: RE: [dts][PATCH V1 2/6] tests/kernelpf_vf:add new suite to cover most of the basic vf cases
Date: Wed, 14 Jun 2023 02:03:08 +0000 [thread overview]
Message-ID: <CY5PR11MB6187C83B3B8C0E1C26C7D13DF55AA@CY5PR11MB6187.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230608182742.360594-3-zhiminx.huang@intel.com>
> -----Original Message-----
> From: Zhimin Huang <zhiminx.huang@intel.com>
> Sent: Friday, June 9, 2023 2:28 AM
> To: dts@dpdk.org
> Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
> Subject: [dts][PATCH V1 2/6] tests/kernelpf_vf:add new suite to cover most of
> the basic vf cases
>
> add kernelpf_vf new suite and refactor with func_test_base common module:
> cover kernelpf_iavf/vf_vlan/vf_macfilter/vf_rss/vf_xstats_check.
>
> Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
> ---
> tests/TestSuite_kernelpf_vf.py | 1007 ++++++++++++++++++++++++++++++++
> 1 file changed, 1007 insertions(+)
> create mode 100644 tests/TestSuite_kernelpf_vf.py
>
......
> +
> + def test_vf_multicast(self):
> + self.rxtx_base.launch_testpmd()
> + self.rxtx_base.basic_multicast_check(
> + normal_mac=VF_MAC_ADDR, multicast_mac=MULTICAST_MAC_ADDR
> + )
> +
> + def test_vf_broadcast(self):
> + self.rxtx_base.launch_testpmd()
> + self.rxtx_base.basic_rx_check(packets_num=1,
> + packet_dst_mac=BROADCAST_MAC_ADDR)
I don't think it is a good idea to launch testpmd in every single case. It costs a lot of time.
A good suite and cases organization could avoid this and save a lot of execution time.
1. adjust test cases that could use same args for testpmd.
2. separate those testpmd with different args to other suites.
> +
> + def test_vf_queue_start_stop(self):
> + self.rxtx_base.launch_testpmd()
> + self.rxtx_base.basic_macfwd_check(
> + packet_num=4, dst_mac=VF_MAC_ADDR,
> rx_port=self.used_dut_rx_port
> + )
> + packets_captured, _, stats = self.rxtx_base.execute_fwd_check_process(
> + packets=self.rxtx_base.generate_random_packets(
> + dstmac=VF_MAC_ADDR, pktnum=4
> + ),
> + rx_port=self.used_dut_rx_port,
> + pmd_commands=["stop", "port 0 rxq 0 stop", "start"],
> + )
> + self.verify(
> + len(packets_captured) == 0
> + and stats[self.used_dut_rx_port]["TX-packets"] == 0,
> + "receive packet num is not match",
> + )
> + packets_captured, _, stats = self.rxtx_base.execute_fwd_check_process(
> + packets=self.rxtx_base.generate_random_packets(
> + dstmac=VF_MAC_ADDR, pktnum=4
> + ),
> + rx_port=self.used_dut_rx_port,
> + pmd_commands=["stop", "port 0 rxq 0 start", "port 1 txq 0 stop",
> "start"],
> + )
> + self.verify(
> + len(packets_captured) == 0
> + and stats[self.used_dut_rx_port]["TX-packets"] == 0,
> + "receive packet num is not match",
> + )
> + self.rxtx_base.basic_macfwd_check(
> + packet_num=4,
> + dst_mac=VF_MAC_ADDR,
> + rx_port=self.used_dut_rx_port,
> + pmd_commands=["stop", "port 1 txq 0 start", "start"],
> + )
> +
next prev parent reply other threads:[~2023-06-14 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 18:27 [dts][PATCH V1 0/6] add new common module and add new suites Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 1/6] tests/func_test_base:add new commom module to refactor func test cases Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 2/6] tests/kernelpf_vf:add new suite to cover most of the basic vf cases Zhimin Huang
2023-06-14 2:03 ` Tu, Lijuan [this message]
2023-06-08 18:27 ` [dst][PATCH V1 3/6] test_plans/kernelpf_vf_test_plan:add new plan " Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 4/6] tests/ice_kernelpf_dcf:add new suite to cover dcf pmd function Zhimin Huang
2023-06-08 18:27 ` [dst][PATCH V1 5/6] test_plans/ice_kernelpf_dcf_test_plan:add new plan to cover the most of " Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 6/6] conf/*:add config file for new suites Zhimin Huang
2023-06-09 9:22 ` Peng, Yuan
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=CY5PR11MB6187C83B3B8C0E1C26C7D13DF55AA@CY5PR11MB6187.namprd11.prod.outlook.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=zhiminx.huang@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).