From: "peng,zhang" <peng1x.zhang@intel.com> To: dts@dpdk.org Cc: "peng,zhang" <peng1x.zhang@intel.com>, peng@dpdk.org Subject: [dts] [PATCH V1] test_plans/vmdq_test_plan:modify testplan and testcase Date: Wed, 12 Jan 2022 13:54:46 +0800 Message-ID: <20220112055446.213883-1-peng1x.zhang@intel.com> (raw) Delete useless change of 'MAX_QUEUES' for testplan and testcase because the 'MAX_QUEUES' is already 1024 in current dpdk. Signed-off-by: peng,zhang <peng1x.zhang@intel.com> --- test_plans/vmdq_test_plan.rst | 5 ----- tests/TestSuite_vmdq.py | 2 -- 2 files changed, 7 deletions(-) diff --git a/test_plans/vmdq_test_plan.rst b/test_plans/vmdq_test_plan.rst index 2734b0c0..ef64823c 100644 --- a/test_plans/vmdq_test_plan.rst +++ b/test_plans/vmdq_test_plan.rst @@ -67,11 +67,6 @@ Prerequisites 52:54:00:12:[port_index]:00 to 52:54:00:12:[port_index]:3e and the VLAN user priority field increments from 0 to 7 (inclusive) for each VLAN ID. In our case port_index = 0 or 1. --Case config:: - If test max queues per port 1024, need to set the "CONFIG_RTE_MAX_QUEUES_PER_PORT=1024" in ./config/common_base, - and need to set the "define MAX_QUEUES 1024" in ./examples/vmdq/main.c and re-build DPDK. - Note: different NIC, the MAX_QUEUES is different, eg: Fortville is 1024. - Test Case: Measure VMDQ pools queues ------------------------------------ 1. Put different number of pools: in the case of 10G 82599 Nic is 64, in the case diff --git a/tests/TestSuite_vmdq.py b/tests/TestSuite_vmdq.py index 1c8671b5..83da6be0 100644 --- a/tests/TestSuite_vmdq.py +++ b/tests/TestSuite_vmdq.py @@ -57,8 +57,6 @@ class TestVmdq(TestCase): self.ports_socket = self.dut.get_numa_id(self.dut_ports[0]) self.dut.build_install_dpdk(self.target) - # Update the max queue per port for Fortville. - self.dut.send_expect("sed -i 's/define MAX_QUEUES 128/define MAX_QUEUES 1024/' ./examples/vmdq/main.c", "#", 5) # out = self.dut.send_expect("make -C examples/vmdq", "#", 10) out = self.dut.build_dpdk_apps('examples/vmdq') self.verify("Error" not in out, "Compilation error") -- 2.25.1
next reply other threads:[~2022-01-12 5:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 5:54 peng,zhang [this message] 2022-01-12 7:26 ` Zhang, Peng1X 2022-01-12 7:43 ` 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=20220112055446.213883-1-peng1x.zhang@intel.com \ --to=peng1x.zhang@intel.com \ --cc=dts@dpdk.org \ --cc=peng@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
test suite reviews and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dts/0 dts/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dts dts/ http://inbox.dpdk.org/dts \ dts@dpdk.org public-inbox-index dts Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dts AGPL code for this site: git clone https://public-inbox.org/public-inbox.git