From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Andrew Rybchenko <arybchenko@solarflare.com>
Subject: RE: [PATCH] net/bonding: fix MTU set for slaves
Date: Thu, 27 Jan 2022 04:07:52 +0000 [thread overview]
Message-ID: <BYAPR11MB2711B56AEA7314706EF64C59FE219@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220126131037.2403369-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Wednesday, January 26, 2022 9:11 PM
> To: Chas Williams <chas3@att.com>; Min Hu (Connor)
> <humin29@huawei.com>; Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>;
> Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; stable@dpdk.org;
> Andrew Rybchenko <arybchenko@solarflare.com>; Jiang, YuX
> <yux.jiang@intel.com>
> Subject: [PATCH] net/bonding: fix MTU set for slaves
>
> ethdev requires device to be configured before setting MTU.
>
> In bonding PMD, while configuring slaves, bonding first sets MTU later
> configures them, which causes failure if slaves are not configured in advance.
>
> Fixing by changing the order in slave configure as requested in ethdev layer,
> configure first and set MTU later.
>
> Bugzilla ID: 864
> Fixes: b26bee10ee37 ("ethdev: forbid MTU set before device configure")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
Tested-by: Yu Jiang <YuX.Jiang@intel.com>
> Cc: Andrew Rybchenko <arybchenko@solarflare.com>
> Cc: yux.jiang@intel.com
> ---
Verified patchset https://patches.dpdk.org/project/dpdk/patch/20220126131037.2403369-1-ferruh.yigit@intel.com/ on baseline v22.03-rc0's 8a5a91401d .
Tested pass on nic Ethernet Connection X722 for 10GbE SFP+ 37d0/Ubuntu21.10,5.13.0-19-generic
next prev parent reply other threads:[~2022-01-27 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 13:10 Ferruh Yigit
2022-01-27 4:07 ` Jiang, YuX [this message]
2022-01-27 9:18 ` Min Hu (Connor)
2022-02-01 11:44 ` Ferruh Yigit
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=BYAPR11MB2711B56AEA7314706EF64C59FE219@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=arybchenko@solarflare.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--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).