From: "Zhang, Peng1X" <peng1x.zhang@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/i40e: enable max frame size at port level
Date: Mon, 21 Feb 2022 10:42:34 +0000 [thread overview]
Message-ID: <CO1PR11MB51057617A3C1D25BB3161A33CE3A9@CO1PR11MB5105.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB27110434B9262C0E2BED3AD3FE3A9@BYAPR11MB2711.namprd11.prod.outlook.com>
> -----Original Message-----
> From: dapengx.yu@intel.com <dapengx.yu@intel.com>
> Sent: Tuesday, December 7, 2021 5:00 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Yu, DapengX <dapengx.yu@intel.com>; stable@dpdk.org
> Subject: [PATCH] net/i40e: enable max frame size at port level
>
> From: Dapeng Yu <dapengx.yu@intel.com>
>
> Currently max frame size is set at queue level, which makes the values of the
> following counters wrong when a jumbo frame is received.
>
> The expected value:
> rx_good_bytes: 0
> rx_errors: 1
> rx_oversize_errors: 1
>
> The actual value:
> rx_good_bytes: 1626
> rx_errors: 0
> rx_oversize_errors: 0
>
> This patch enables setting max frame size at port level, and makes the values
> above right.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Dapeng Yu <dapengx.yu@intel.com>
> --
Tested-by: Peng Zhang <peng1x.zhang@intel.com>
next prev parent reply other threads:[~2022-02-21 10:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 8:59 dapengx.yu
[not found] ` <BYAPR11MB2711AB91F380189FB6AFCC52FE359@BYAPR11MB2711.namprd11.prod.outlook.com>
[not found] ` <BYAPR11MB27110434B9262C0E2BED3AD3FE3A9@BYAPR11MB2711.namprd11.prod.outlook.com>
2022-02-21 9:28 ` Zhang, Peng1X
2022-02-21 10:42 ` Zhang, Peng1X [this message]
2022-02-21 11:22 ` Zhang, Qi Z
2022-02-22 9:52 ` Kevin Traynor
2022-12-12 13:53 ` David Marchand
2022-12-12 13:58 ` David Marchand
2022-12-12 14:37 ` [PATCH] net/i40e: drop link check when configuring frame size David Marchand
2022-12-13 9:18 ` [PATCH v2] net/i40e: don't check link status on device start David Marchand
2023-01-03 14:02 ` David Marchand
2023-01-09 9:21 ` David Marchand
2023-01-13 13:33 ` David Marchand
2023-01-13 13:39 ` Zhang, Helin
2023-01-13 13:46 ` David Marchand
2023-01-13 13:50 ` Zhang, Helin
2023-01-13 13:53 ` David Marchand
2023-01-16 11:02 ` Su, Simei
2023-02-07 11:31 ` Thomas Monjalon
2023-02-07 14:05 ` Su, Simei
2023-03-06 6:53 ` Su, Simei
2023-03-06 11:05 ` Zhang, Qi Z
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=CO1PR11MB51057617A3C1D25BB3161A33CE3A9@CO1PR11MB5105.namprd11.prod.outlook.com \
--to=peng1x.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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 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).