From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V3 0/13] l3fwd: refactor script
Date: Thu, 16 Jan 2020 07:15:23 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBAB6FC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200116052820.21902-1-yufengx.mo@intel.com>
Hi Feng,
Applied the patch set failed because code base changed. Could you please rework it ?
thanks
> -----Original Message-----
> From: Mo, YufengX
> Sent: Thursday, January 16, 2020 1:28 PM
> To: dts@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V3 0/13] l3fwd: refactor script
>
> refactor script.
>
>
> v3:
> - support one port testing topo for ixia.
> - add test case name in cfg file.
> - rename module l3fwd.py to l3fwd_base.py.
> - rename common_l3fwd.cfg to l3fwd_base.cfg.
> - rename verify method names.
> - rename test scripts suite name.
> -
>
> v2:
> - update script based on version 2 l3fwd test plan.
> - separate script into five suites for different testing scenario.
> - separate flows configuration in common_l3fwd.cfg.
> - add test result data check process as new test plan requirement.
> - save test results in json format file.
> -
>
> v1:
> - optimize packet creation time consumption.
> - separate LPM/EM mode packet creation process.
> - use new pktgen coding style to take the place of migration coding style.
> - unify rfc2544/throughput result data display table methods.
> - move test content configuration into cfg file, including flows/EM table/LPM
> table/framesizes/port configs.
>
> yufengmx (13):
> conf/l3fwd: l3fwd suite testing configuration
> conf/l3fwd_base: l3fwd base class flows configuration
> conf/l3fwd_em: suite testing configuration
> conf/l3fwd_lpm_ipv4_rfc2544: suite testing configuration
> conf/l3fwd_lpm_ipv4: l3fwd_lpm_ipv4 testing configuration
> conf/l3fwd_lpm_ipv6: suite testing configuration
> tests/l3fwd: upload automation script
> tests/l3fwd_em: upload automation script
> tests/l3fwd_lpm_ipv4_rfc2544: upload automation script
> tests/l3fwd_lpm_ipv4: upload automation script
> tests/l3fwd_lpm_ipv6: upload automation script
> tests/l3fwd_base: upload automation script
> framework/test_case: add wirespeed columbiaville nic
>
> conf/l3fwd.cfg | 400 ++++++++++++
> conf/l3fwd_base.cfg | 103 +++
> conf/l3fwd_em.cfg | 147 +++++
> conf/l3fwd_lpm_ipv4.cfg | 105 +++
> conf/l3fwd_lpm_ipv4_rfc2544.cfg | 105 +++
> conf/l3fwd_lpm_ipv6.cfg | 105 +++
> framework/test_case.py | 4 +
> tests/TestSuite_l3fwd.py | 370 ++---------
> tests/TestSuite_l3fwd_em.py | 258 +-------
> tests/TestSuite_l3fwd_lpm_ipv4.py | 86 +++
> tests/TestSuite_l3fwd_lpm_ipv4_rfc2544.py | 86 +++
> tests/TestSuite_l3fwd_lpm_ipv6.py | 85 +++
> tests/l3fwd_base.py | 744 ++++++++++++++++++++++
> 13 files changed, 2044 insertions(+), 554 deletions(-) create mode 100644
> conf/l3fwd.cfg create mode 100644 conf/l3fwd_base.cfg create mode
> 100644 conf/l3fwd_em.cfg create mode 100644 conf/l3fwd_lpm_ipv4.cfg
> create mode 100644 conf/l3fwd_lpm_ipv4_rfc2544.cfg create mode 100644
> conf/l3fwd_lpm_ipv6.cfg create mode 100644
> tests/TestSuite_l3fwd_lpm_ipv4.py create mode 100644
> tests/TestSuite_l3fwd_lpm_ipv4_rfc2544.py
> create mode 100644 tests/TestSuite_l3fwd_lpm_ipv6.py create mode
> 100644 tests/l3fwd_base.py
>
> --
> 2.21.0
next prev parent reply other threads:[~2020-01-16 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 5:28 yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 1/13] conf/l3fwd: l3fwd suite testing configuration yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 2/13] conf/l3fwd_base: l3fwd base class flows configuration yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 3/13] conf/l3fwd_em: suite testing configuration yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 4/13] conf/l3fwd_lpm_ipv4_rfc2544: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 5/13] conf/l3fwd_lpm_ipv4: l3fwd_lpm_ipv4 " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 6/13] conf/l3fwd_lpm_ipv6: suite " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 7/13] tests/l3fwd: upload automation script yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 8/13] tests/l3fwd_em: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 9/13] tests/l3fwd_lpm_ipv4_rfc2544: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 0/13] tests/l3fwd_lpm_ipv4: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 1/13] tests/l3fwd_lpm_ipv6: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 2/13] tests/l3fwd_base: " yufengmx
2020-01-16 5:28 ` [dts] [PATCH V3 3/13] framework/test_case: add wirespeed columbiaville nic yufengmx
2020-01-16 7:15 ` Tu, Lijuan [this message]
2020-01-16 7:27 [dts] [PATCH V3 0/13] l3fwd: refactor script yufengmx
2020-01-16 8: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=8CE3E05A3F976642AAB0F4675D0AD20E0BBAB6FC@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).