DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Min, JiaqiX" <jiaqix.min@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: add known issue for ice
Date: Tue, 15 Oct 2019 01:49:19 +0000	[thread overview]
Message-ID: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A55916E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191014182223.35251-1-jiaqix.min@intel.com>


> -----Original Message-----
> From: Min, JiaqiX
> Sent: Tuesday, October 15, 2019 2:22 AM
> To: dev@dpdk.org; Yang, Qiming <qiming.yang@intel.com>
> Cc: Min, JiaqiX <jiaqix.min@intel.com>
> Subject: [PATCH] doc: add known issue for ice
> 
> Add known issue for incorrect Rx statistics when packet is oversize.
> 
> Signed-off-by: Min JiaqiX <jiaqix.min@intel.com>
> ---
>  doc/guides/nics/ice.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/doc/guides/nics/ice.rst b/doc/guides/nics/ice.rst index
> 03819d29f..3e9bc9d33 100644
> --- a/doc/guides/nics/ice.rst
> +++ b/doc/guides/nics/ice.rst
> @@ -127,3 +127,11 @@ The same package file is used by both the kernel
> driver and the DPDK PMD.
>  ~~~~~~~~~~~~~~~~
> 
>  Ice code released in 19.02 is for evaluation only.
> +
> +Incorrect Rx statistics when packet is oversize
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +When a packet is over maximum frame size, the packet is dropped.
> +However, when calling `rte_eth_stats_get`, the Rx statistics will be
> +showed as received.
> +
> --
> 2.17.1

Acked-by: Qiming Yang <qiming.yang@intel.com>

  reply	other threads:[~2019-10-15  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 18:22 Min JiaqiX
2019-10-15  1:49 ` Yang, Qiming [this message]
2019-10-15  2:37   ` Stillwell Jr, Paul M

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=F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A55916E@SHSMSX101.ccr.corp.intel.com \
    --to=qiming.yang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiaqix.min@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).