From: "Liu, Yong" <yong.liu@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Han, YingyaX" <yingyax.han@intel.com>
Subject: Re: [dts] [PATCH V1]tests/shutdown-api: fix the crc-strip issue
Date: Thu, 2 Aug 2018 05:02:51 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E63104EF2@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1533176303-109061-1-git-send-email-yingyax.han@intel.com>
Hi Yingya,
Hex value 0x10000 look wired here, please change the verify message to "CRC keeping not enabled properly" which will be more meaningful.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of han,yingya
> Sent: Thursday, August 02, 2018 10:18 AM
> To: dts@dpdk.org
> Cc: Han, YingyaX <yingyax.han@intel.com>
> Subject: [dts] [PATCH V1]tests/shutdown-api: fix the crc-strip issue
>
> The "disable-crc-strip" parameter was modified in dpdk 18.08.
> The expected value for RX_offloads when crc-strip is off is 0x10000 and when
> crc-strip is on is 0x1000.
> More details can refer to dpdk commit e557ebc0 and DPDK-5829.
> Signed-off-by: han,yingya <yingyax.han@intel.com>
> ---
> tests/TestSuite_shutdown_api.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_shutdown_api.py
> b/tests/TestSuite_shutdown_api.py
> index d00c3fb..3cb0eff 100644
> --- a/tests/TestSuite_shutdown_api.py
> +++ b/tests/TestSuite_shutdown_api.py
> @@ -266,7 +266,7 @@ class TestShutdownApi(TestCase):
> self.pmdout.start_testpmd("Default", "--portmask=%s --port-
> topology=loop --disable-crc-strip" % utils.create_mask(self.ports),
> socket=self.ports_socket)
> out = self.dut.send_expect("show config rxtx", "testpmd> ")
> self.verify(
> - "Rx offloads=0x0" in out, "CRC stripping not disabled properly")
> + "Rx offloads=0x10000" in out, "CRC stripping not disabled
> properly")
>
> self.dut.send_expect("port stop all", "testpmd> ", 100)
> self.dut.send_expect("port config all crc-strip on", "testpmd> ")
> --
> 1.9.3
next prev parent reply other threads:[~2018-08-02 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 2:18 han,yingya
2018-08-02 5:02 ` Liu, Yong [this message]
2018-08-02 6:37 ` Han, YingyaX
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=86228AFD5BCD8E4EBFD2B90117B5E81E63104EF2@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=yingyax.han@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).