From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] replace protocal with protocol in all test plans
Date: Mon, 13 May 2019 02:07:38 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA7F975@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1556565173-13544-1-git-send-email-ramirose@gmail.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Tuesday, April 30, 2019 3:13 AM
> To: dts@dpdk.org
> Cc: Rami Rosen <ramirose@gmail.com>
> Subject: [dts] [PATCH] replace protocal with protocol in all test plans
>
> This patch replaces the word "protocal" with "protocol" in all test plans.
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> test_plans/l3fwdacl_test_plan.rst | 4 ++--
> test_plans/pmd_bonded_8023ad_test_plan.rst | 2 +-
> test_plans/vm2vm_virtio_net_perf_test_plan.rst | 12 ++++++------
> 3 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/test_plans/l3fwdacl_test_plan.rst
> b/test_plans/l3fwdacl_test_plan.rst
> index 5e5b854..9fd5e50 100644
> --- a/test_plans/l3fwdacl_test_plan.rst
> +++ b/test_plans/l3fwdacl_test_plan.rst
> @@ -136,7 +136,7 @@ Ipv4 packet match destination port 101 will be
> dropped::
> Send one ipv4 packet with destination port 101 will be dropped.
> Send one ipv4 packet with destination port 1 will be forwarded to PORT0
>
> -Ipv4 packet match protocal TCP will be dropped::
> +Ipv4 packet match protocol TCP will be dropped::
>
> Add one ACL rule and default route rule in /root/rule_ipv4.db
> @0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 6/0xff @@ -231,7 +231,7 @@ Ipv6
> packet match destination port 101 will be dropped::
> Send one ipv6 packet with destination port 101 will be dropped.
> Send one ipv6 packet with destination port 1 will be forwarded to PORT0
>
> -Ipv6 packet match protocal TCP will be dropped::
> +Ipv6 packet match protocol TCP will be dropped::
>
> Add one ACL rule and default route rule in /root/rule_ipv6.db
> @0:0:0:0:0:0:0:0/0 0:0:0:0:0:0:0:0/0 0 : 65535 0 : 65535 6/0xff diff --git
> a/test_plans/pmd_bonded_8023ad_test_plan.rst
> b/test_plans/pmd_bonded_8023ad_test_plan.rst
> index 4e45e08..45a8fca 100644
> --- a/test_plans/pmd_bonded_8023ad_test_plan.rst
> +++ b/test_plans/pmd_bonded_8023ad_test_plan.rst
> @@ -39,7 +39,7 @@ testpmd.
> link bonding mode 4 is IEEE 802.3ad Dynamic link aggregation. Creates
> aggregation groups that share the same speed and duplex settings. Utilizes
> all slaves in the active aggregator according to the 802.3ad specification.
> DPDK -realize it based on 802.1AX specification, it includes LACP protocal and
> Marker
> +realize it based on 802.1AX specification, it includes LACP protocol
> +and Marker
> protocol. This mode requires a switch that supports IEEE 802.3ad Dynamic
> link aggregation.
>
> diff --git a/test_plans/vm2vm_virtio_net_perf_test_plan.rst
> b/test_plans/vm2vm_virtio_net_perf_test_plan.rst
> index 6ae4339..a822e49 100644
> --- a/test_plans/vm2vm_virtio_net_perf_test_plan.rst
> +++ b/test_plans/vm2vm_virtio_net_perf_test_plan.rst
> @@ -74,12 +74,12 @@ Test Case 1: vhost-user + virtio-net VM2VM with tcp
> traffic
> -device virtio-net-
> pci,mac=52:54:00:00:00:02,netdev=mynet2,mrg_rxbuf=on,csum=on,gso=on,g
> uest_csum=on,host_tso4=on,guest_tso4=on,guest_ecn=on \
> -vnc :11 -daemonize
>
> -3. On VM1, set virtio device IP and run arp protocal::
> +3. On VM1, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.2
> arp -s 1.1.1.8 52:54:00:00:00:02
>
> -4. On VM2, set virtio device IP and run arp protocal::
> +4. On VM2, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.8
> arp -s 1.1.1.2 52:54:00:00:00:01
> @@ -124,12 +124,12 @@ Test Case 2: vhost-user + virtio-net VM2VM zero-
> copy with tcp traffic
> -device virtio-net-
> pci,mac=52:54:00:00:00:02,netdev=mynet2,mrg_rxbuf=on,csum=on,gso=on,g
> uest_csum=on,host_tso4=on,guest_tso4=on,guest_ecn=on \
> -vnc :11 -daemonize
>
> -3. On VM1, set virtio device IP and run arp protocal::
> +3. On VM1, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.2
> arp -s 1.1.1.8 52:54:00:00:00:02
>
> -4. On VM2, set virtio device IP and run arp protocal::
> +4. On VM2, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.8
> arp -s 1.1.1.2 52:54:00:00:00:01
> @@ -174,12 +174,12 @@ Test Case 3: vhost-user + virtio-net VM2VM with
> udp traffic
> -device virtio-net-
> pci,mac=52:54:00:00:00:02,netdev=mynet2,mrg_rxbuf=on,csum=on,guest_csu
> m=on,host_tso4=on,guest_tso4=on,guest_ecn=on,guest_ufo=on,host_ufo=o
> n \
> -vnc :11 -daemonize
>
> -3. On VM1, set virtio device IP and run arp protocal::
> +3. On VM1, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.2
> arp -s 1.1.1.8 52:54:00:00:00:02
>
> -4. On VM2, set virtio device IP and run arp protocal::
> +4. On VM2, set virtio device IP and run arp protocol::
>
> ifconfig ens3 1.1.1.8
> arp -s 1.1.1.2 52:54:00:00:00:01
> --
> 1.8.3.1
prev parent reply other threads:[~2019-05-13 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:12 Rami Rosen
2019-05-13 2:07 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA7F975@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ramirose@gmail.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).