DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemming@brocade.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ixgbe: fix crc-strip enable changing rx bytes
Date: Mon, 9 Nov 2015 08:32:09 -0800	[thread overview]
Message-ID: <20151109083209.7c1eb27b@xeon-e3> (raw)
In-Reply-To: <1447080904-27512-1-git-send-email-harry.van.haaren@intel.com>

On Mon, 9 Nov 2015 14:55:04 +0000
Harry van Haaren <harry.van.haaren@intel.com> wrote:

> Fix a consistency issue in ixgbe, that when CRC stripping is enabled,
> the CRC bytes are not added to the rx total byte count. When CRC strip
> is disabled, these bytes are counted.
> 
> This patch reads the CRC strip register, and when enabled adds 4 bytes
> to the total bytes recieved counter for each received packet.
> 
> E-mail discussion thread available:
> http://dpdk.org/ml/archives/dev/2015-March/015685.html
> 
> To reproduce, run testpmd with no flags and with --crc-strip, sending a
> single packet, and notice that the RX byte counter is 4 bytes smaller
> when CRC stripping is enabled.
> 
> Fixes: 29a05247ebad ("ixgbe: configure CRC stripping behaviour of PF")
> 
> Reported-by: Stephen Hemminger <shemming@brocade.com>
> Suggested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> ---
>  doc/guides/rel_notes/release_2_2.rst | 6 ++++++
>  drivers/net/ixgbe/ixgbe_ethdev.c     | 7 +++++++
>  2 files changed, 13 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst
> index 59dda59..6bab51b 100644
> --- a/doc/guides/rel_notes/release_2_2.rst
> +++ b/doc/guides/rel_notes/release_2_2.rst
> @@ -134,6 +134,12 @@ Drivers
>  
>    VF needs the PF interrupt support initialized even if not started.
>  
> +* **ixgbe: Fixed CRC strip enable influencing RX byte counters.**
> +
> +  A workaround has been put in place to ensure consistent presentation
> +  of total RX bytes. The CRC bytes are now always included in RX bytes,
> +  providing consistency between RX and TX bytes.
> +
>  * **i40e: Fixed base driver allocation when not using first numa node.**
>  
>    Fixed i40e issue that occurred when a DPDK application didn't initialize
> diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
> index 0b0bbcf..b311ffb 100644
> --- a/drivers/net/ixgbe/ixgbe_ethdev.c
> +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
> @@ -2361,6 +2361,13 @@ ixgbe_read_stats_registers(struct ixgbe_hw *hw, struct ixgbe_hw_stats
>  	hw_stats->mrfc += IXGBE_READ_REG(hw, IXGBE_MRFC);
>  	hw_stats->rlec += IXGBE_READ_REG(hw, IXGBE_RLEC);
>  
> +	/* Workaround for RX byte count not including CRC bytes when CRC
> +	 * strip is enabled. Multiply rx_total_packets by CRC size and add
> +	 * to adjust rx_bytes to the correct value
> +	 */
> +	if (IXGBE_READ_REG(hw, IXGBE_HLREG0) & IXGBE_HLREG0_RXCRCSTRP)
> +		*total_qbrc += (*total_qprc * 4);
> +
>  	/* Note that gprc counts missed packets */
>  	hw_stats->gprc += IXGBE_READ_REG(hw, IXGBE_GPRC);
>  

NAK.

The CRC should never be part of rx/tx statistics.

The problem with putting CRC in statistics is the behavior introduces a
device and setting dependency. This is a disaster for generic programs (like vRouter)
that want to work across multiple hardware and virtual NIC's.

Also, Linux, BSD, and Unix do not include CRC in reported bytes for network
interfaces.

Please fix up my original patch to work for both settings, or I can do it.

  reply	other threads:[~2015-11-09 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 14:55 Harry van Haaren
2015-11-09 16:32 ` Stephen Hemminger [this message]
2015-11-10 15:46   ` Van Haaren, Harry

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=20151109083209.7c1eb27b@xeon-e3 \
    --to=shemming@brocade.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@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).