From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V6 0/1] l3fwd: update json and display
Date: Fri, 7 Aug 2020 13:07:07 +0800 [thread overview]
Message-ID: <20200807050708.32412-1-yufengx.mo@intel.com> (raw)
update json and display.
v6:
- fix comment error.
v5:
- change config line rate % value to config value, which config in l3fwd_lpm_ipv4_rfc2544.cfg
- chang expected throughput to nic theory line x rate config line rate(% percentage) / 100.
v4:
- rebase source code
v3:
- change Actual line rate (Mpps) --> Actual Throughput (Mpps).
v2:
- update rfc2544 json and display.
v1:
- update throughput delta, Throughput delta = run value - expected value
yufengmx (1):
l3fwd: update rfc2544/throughput json and display
tests/l3fwd_base.py | 26 +++++++++++++++++++-------
1 file changed, 19 insertions(+), 7 deletions(-)
--
2.21.0
next reply other threads:[~2020-08-07 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 5:07 yufengmx [this message]
2020-08-07 5:07 ` [dts] [PATCH V6 1/1] l3fwd: update rfc2544/throughput " 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=20200807050708.32412-1-yufengx.mo@intel.com \
--to=yufengx.mo@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).