All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 597] PCAP PMD reports incorrect TX stats when sending jumbo frames
Date: Mon, 07 Dec 2020 14:42:49 +0000	[thread overview]
Message-ID: <bug-597-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=597

            Bug ID: 597
           Summary: PCAP PMD reports incorrect TX stats when sending jumbo
                    frames
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: cian.ferriter@intel.com
  Target Milestone: ---

When the PCAP PMD TXes jumbo frames to a file, the wrong tx bytes size is
reported.

In the below example, 2 packets are in the RX PCAP file. The RX-bytes are
reported correctly since each packet is 65535 Bytes.

Port statistics ====================================
  ######################## NIC statistics for port 0  ########################
  RX-packets: 2          RX-missed: 0          RX-bytes:  131070
  RX-errors: 0
  RX-nombuf:  0
  TX-packets: 2          TX-errors: 0          TX-bytes:  32256

  Throughput (since last show)
  Rx-pps:            1          Rx-bps:      1048400
  Tx-pps:            1          Tx-bps:       258008
  ############################################################################

TX_bytes is wrong. It's value is set by "RTE_ETHER_MAX_JUMBO_FRAME_LEN" which
is 16128.

#define RTE_ETHER_MAX_JUMBO_FRAME_LEN \
    0x3F00 /**< Maximum Jumbo frame length, including CRC. */

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-12-07 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-597-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.