From: "Yuan, DukaiX" <dukaix.yuan@intel.com>
To: "Wang, Jie1X" <jie1x.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, SteveX" <stevex.yang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Yuying" <yuying.zhang@intel.com>,
"Wang, Jie1X" <jie1x.wang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/i40e: fix X722 NIC receives jumbo frame packets
Date: Thu, 10 Nov 2022 05:59:44 +0000 [thread overview]
Message-ID: <CH2PR11MB448701A6699F3B781A6C2AE5E8019@CH2PR11MB4487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221110034524.467431-1-jie1x.wang@intel.com>
> -----Original Message-----
> From: Jie Wang <jie1x.wang@intel.com>
> Sent: 2022年11月10日 11:45
> To: dev@dpdk.org
> Cc: Yang, SteveX <stevex.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>; Yang, Qiming <qiming.yang@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Zhang, Yuying <yuying.zhang@intel.com>; Wang,
> Jie1X <jie1x.wang@intel.com>; stable@dpdk.org
> Subject: [PATCH] net/i40e: fix X722 NIC receives jumbo frame packets
>
> For NIC I40E_10G-10G_BASE_T_X722, when the port is configured with link
> speed, it cannot receive jumbo frame packets.
>
> Because it set maximum frame size failed when starts the port that the port
> link status is still down.
>
> This patch fix the error that starts the port will force set maximum frame size.
>
> Fixes: 2184f7cdeeaa ("net/i40e: fix max frame size config at port level")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jie Wang <jie1x.wang@intel.com>
> ---
Tested-by: Dukai Yuan<dukaix.yuan@intel.com>
next prev parent reply other threads:[~2022-11-10 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 3:45 Jie Wang
2022-11-10 5:59 ` Yuan, DukaiX [this message]
2022-11-10 9:47 ` Zhang, Qi Z
2022-12-05 11:15 ` David Marchand
2022-12-05 12:02 ` Kevin Traynor
2022-12-06 0:01 ` Zhang, Qi Z
2022-12-06 10:12 ` Kevin Traynor
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=CH2PR11MB448701A6699F3B781A6C2AE5E8019@CH2PR11MB4487.namprd11.prod.outlook.com \
--to=dukaix.yuan@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jie1x.wang@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=yuying.zhang@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).