patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Kevin Traynor <ktraynor@redhat.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Yuan, DukaiX" <dukaix.yuan@intel.com>,
	"Wang, Jie1X" <jie1x.wang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "Yang, SteveX" <stevex.yang@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Zhang, Yuying" <yuying.zhang@intel.com>
Subject: Re: [PATCH] net/i40e: fix X722 NIC receives jumbo frame packets
Date: Mon, 5 Dec 2022 12:15:04 +0100	[thread overview]
Message-ID: <CAJFAV8wbCDA6q0F8hF4g7ZhWB9YuBRn52sXXyhJPGvuWs2k9Rw@mail.gmail.com> (raw)
In-Reply-To: <DM4PR11MB59941C506DDB329F6E26CB18D7019@DM4PR11MB5994.namprd11.prod.outlook.com>

Hi Kevin, Qi,

On Thu, Nov 10, 2022 at 10:48 AM Zhang, Qi Z <qi.z.zhang@intel.com> wrote:
> > > 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>

It seems this fix has been missed in 21.11 (for the reason we
discussed with Kevin offlist).

Our QE reported that reception of jumbo frames seems broken in the 21.11 branch.

I can reproduce with a X710 nic: v21.11.0 is fine, but v21.11.1 and
v21.11.2 show the following error log.
Dec 05 05:41:37 xxx ovs-vswitchd[53585]:
ovs|00183|dpdk|ERR|i40e_set_mac_max_frame(): Set max frame size at
port level not applicable on link down

The log goes away with backporting this current patch.
Can this be added to 21.11 queue, and have Intel validate this issue?

Thanks!


-- 
David Marchand


  reply	other threads:[~2022-12-05 11:15 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
2022-11-10  9:47   ` Zhang, Qi Z
2022-12-05 11:15     ` David Marchand [this message]
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=CAJFAV8wbCDA6q0F8hF4g7ZhWB9YuBRn52sXXyhJPGvuWs2k9Rw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=dukaix.yuan@intel.com \
    --cc=jie1x.wang@intel.com \
    --cc=ktraynor@redhat.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).