test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lei.a.yao@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/power_empty_poll: add suite cfg file
Date: Mon, 22 Jun 2020 13:59:34 +0800	[thread overview]
Message-ID: <20200622055935.12025-2-yufengx.mo@intel.com> (raw)
In-Reply-To: <20200622055935.12025-1-yufengx.mo@intel.com>


select traffic frame size in suite cfg file.

Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
 tests/TestSuite_power_empty_poll.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/TestSuite_power_empty_poll.py b/tests/TestSuite_power_empty_poll.py
index 7b35b9d..93843f7 100644
--- a/tests/TestSuite_power_empty_poll.py
+++ b/tests/TestSuite_power_empty_poll.py
@@ -141,7 +141,7 @@ class TestPowerEmptyPoll(TestCase):
                 'type': 'UDP',
                 'pkt_layers': {
                     'ipv4': {'dst': '1.1.1.1'},
-                    'raw': {'payload': ['58'] * self.get_pkt_len('udp', frame_size=1024)}}},
+                    'raw': {'payload': ['58'] * self.get_pkt_len('udp', frame_size=self.frame_size)}}},
         }
         # create packet instance for send
         streams = []
@@ -390,6 +390,8 @@ class TestPowerEmptyPoll(TestCase):
     def preset_test_environment(self):
         self.is_l3fwd_on = None
         self.cpu_info, self.base_freqs_info = self.get_all_cpu_attrs()
+        test_content = self.get_suite_cfg()
+        self.frame_size = test_content.get('frame_size') or 1024
         self.check_core = self.get_normal_cores_index(2)
         self.verify_hyper_threading()
         # modprobe msr module to let the application can get the CPU HW info
-- 
2.21.0


  reply	other threads:[~2020-06-22  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  5:59 [dts] [PATCH V1 0/2] " yufengmx
2020-06-22  5:59 ` yufengmx [this message]
2020-06-22  5:59 ` [dts] [PATCH V1 2/2] " yufengmx

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=20200622055935.12025-2-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@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).