From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] test_plans checksum_offload: fix name of a parameter
Date: Mon, 4 Mar 2019 06:47:54 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA3CE3C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1551629272-8610-1-git-send-email-ramirose@gmail.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Monday, March 4, 2019 12:08 AM
> To: dts@dpdk.org
> Cc: Rami Rosen <ramirose@gmail.com>
> Subject: [dts] [PATCH] test_plans checksum_offload: fix name of a parameter
>
> Testpmd has no longer a paramater called enable-rx-checksum, it should be:
> enable-rx-cksum. This patch fixes it in the checksum offload test plan.
>
> See:
> https://git.dpdk.org/dpdk/tree/app/test-pmd/parameters.c#n134
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> test_plans/checksum_offload_test_plan.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/test_plans/checksum_offload_test_plan.rst
> b/test_plans/checksum_offload_test_plan.rst
> index 710b98a..82fd12f 100644
> --- a/test_plans/checksum_offload_test_plan.rst
> +++ b/test_plans/checksum_offload_test_plan.rst
> @@ -56,7 +56,7 @@ On the TX side:
> RX side, the L3/L4 checksum offload by hardware can be enabled with the
> following command of the ``testpmd`` application::
>
> - enable-rx-checksum
> + enable-rx-cksum
>
> TX side, the insertion of a L3/L4 checksum by hardware can be enabled with the
> following command of the ``testpmd`` application and running in a dedicated
> @@ -93,7 +93,7 @@ launch the ``testpmd`` with the following arguments::
>
> ./build/app/testpmd -cffffff -n 1 -- -i --burst=1 --txpt=32 \
> --txht=8 --txwt=0 --txfreet=0 --rxfreet=64 --mbcache=250 --portmask=0x5
> - enable-rx-checksum
> + enable-rx-cksum
>
> Set the verbose level to 1 to display information for each received packet::
>
> --
> 1.8.3.1
prev parent reply other threads:[~2019-03-04 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 16:07 Rami Rosen
2019-03-04 6:47 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA3CE3C@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).