test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Peng, ZhihongX" <zhihongx.peng@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, ZhihongX" <zhihongx.peng@intel.com>
Subject: Re: [dts] [PATCH V2] Modify the clv offset code
Date: Tue, 22 Oct 2019 09:51:13 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB450D9@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191021112143.27230-1-zhihongx.peng@intel.com>

I can't understand why is the patch, thanks

Columbiaville and Fortville has the same overhead length, so why they are in different catalogs.
#define ICE_ETH_OVERHEAD \
        (RTE_ETHER_HDR_LEN + RTE_ETHER_CRC_LEN + ICE_VLAN_TAG_SIZE * 2)

#define I40E_ETH_OVERHEAD \
        (RTE_ETHER_HDR_LEN + RTE_ETHER_CRC_LEN + I40E_VLAN_TAG_SIZE * 2)


> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Zhihong
> Sent: Monday, October 21, 2019 7:22 PM
> To: dts@dpdk.org
> Cc: Peng, ZhihongX <zhihongx.peng@intel.com>
> Subject: [dts] [PATCH V2] Modify the clv offset code
> 
> Signed-off-by: Peng Zhihong <zhihongx.peng@intel.com>
> ---
>  tests/TestSuite_userspace_ethtool.py | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/TestSuite_userspace_ethtool.py
> b/tests/TestSuite_userspace_ethtool.py
> index 116fd3a..94918e9 100644
> --- a/tests/TestSuite_userspace_ethtool.py
> +++ b/tests/TestSuite_userspace_ethtool.py
> @@ -546,9 +546,16 @@ class TestUserspaceEthtool(TestCase,
> IxiaPacketGenerator):
>          mtus = [1519, 2048]
>          mtu_threshold = 2022
>          offset = 0
> +
>          if self.nic in ['powerville', 'springville']:
>              mtu_threshold = 2026
>              offset = 4
> +        elif self.nic in ['columbiaville_25g', 'columbiaville_100g']:
> +            #ICE_ETH_OVERHEAD is 8
> +            offset = 8
> +        else:
> +            pass
> +
>          for index in range(len(self.ports)):
>              port = self.ports[index]
>              # change mtu
> @@ -561,10 +568,9 @@ class TestUserspaceEthtool(TestCase,
> IxiaPacketGenerator):
>                  if mtu > mtu_threshold:
>                      if self.nic in ['powerville', 'springville']:
>                          mtu = mtu_threshold
> -                    self.dut.send_expect("stop %s" % index, "EthApp>")
> -                    self.dut.send_expect("mtu %d %d" % (index, mtu), "EthApp>")
> -                    self.dut.send_expect("open %s" % index, "EthApp>")
> +                self.dut.send_expect("stop %s" % index, "EthApp>")
>                  self.dut.send_expect("mtu %d %d" % (index, mtu), "EthApp>")
> +                self.dut.send_expect("open %s" % index, "EthApp>")
>                  time.sleep(5)
>                  ori_rx_pkts, _ = self.strip_portstats(index)
>                  pkt_size = mtu + HEADER_SIZE['eth'] + offset
> --
> 2.17.1


  reply	other threads:[~2019-10-22  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 11:21 Peng Zhihong
2019-10-22  9:51 ` Tu, Lijuan [this message]
2019-10-22  9:56   ` Peng, ZhihongX
2019-10-22  9:59   ` Peng, ZhihongX
  -- strict thread matches above, loose matches on Subject: below --
2019-10-21 10:24 Peng Zhihong
2019-10-21  2:30 ` Ma, LihongX

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=8CE3E05A3F976642AAB0F4675D0AD20E0BB450D9@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=zhihongx.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).