From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH v1]test_plans: add two nic type to ipgre_test_plan.rst
Date: Tue, 24 Sep 2019 09:21:02 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB2777B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1569230627-81350-1-git-send-email-yuan.peng@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Yuan
> Sent: Monday, September 23, 2019 5:24 PM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>
> Subject: [dts] [PATCH v1]test_plans: add two nic type to ipgre_test_plan.rst
>
> Add two nic types to ipgre_test_plan.rst
>
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
>
> diff --git a/test_plans/ipgre_test_plan.rst b/test_plans/ipgre_test_plan.rst
> index 97c4a51..c7ab602 100644
> --- a/test_plans/ipgre_test_plan.rst
> +++ b/test_plans/ipgre_test_plan.rst
> @@ -41,14 +41,14 @@ Fortville support GRE packet detecting, checksum
> computing and filtering.
> Prerequisites
> =============
>
> -Fortville nic should be on the DUT.
> +Fortville/carlsville/columbiaville nic should be on the DUT.
>
> Test Case 1: GRE ipv4 packet detect
> ===================================
>
> Start testpmd and enable rxonly forwarding mode::
>
> - testpmd -c ffff -n 4 -- -i --tx-offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i
> testpmd> set fwd rxonly
> testpmd> set verbose 1
> testpmd> start
> @@ -77,7 +77,7 @@ Test Case 2: GRE ipv6 packet detect
>
> Start testpmd and enable rxonly forwarding mode::
>
> - testpmd -c ffff -n 4 -- -i --tx-offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i --enable-hw-vlan
> testpmd> set fwd rxonly
> testpmd> set verbose 1
> testpmd> start
> @@ -124,7 +124,7 @@ Test Case 3: GRE packet filter
>
> Start testpmd with multi queues::
>
> - testpmd -c ff -n 3 -- -i --rxq=4 --txq=4 --tx-offloads=0x8fff
> + testpmd -c ff -n 3 -- -i --rxq=4 --txq=4
> testpmd> set fwd rxonly
> testpmd> set nbcore 4
> testpmd> set verbose 1
> @@ -161,7 +161,7 @@ Test Case 4: GRE packet chksum offload
>
> Start testpmd with hardware checksum offload enabled::
>
> - testpmd -c ff -n 3 -- -i --tx-offloads=0x8fff --enable-rx-cksum --port-
> topology=loop
> + testpmd -c ff -n 3 -- -i --enable-rx-cksum --port-topology=loop
> testpmd> set verbose 1
> testpmd> set fwd csum
> testpmd> csum set ip hw 0
> --
> 2.7.4
prev parent reply other threads:[~2019-09-24 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 9:23 Peng Yuan
2019-09-24 9:21 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BB2777B@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).