DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>,
	Chas Williams <chas3@att.com>,
	Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	<yux.jiang@intel.com>
Subject: Re: [PATCH] net/bonding: fix MTU set for slaves
Date: Tue, 1 Feb 2022 11:44:53 +0000	[thread overview]
Message-ID: <b4fc47a6-e5be-3e34-7233-0a1b0020ab07@intel.com> (raw)
In-Reply-To: <24dfb8f2-6d56-e091-7b7d-b88e18121749@huawei.com>

On 1/27/2022 9:18 AM, Min Hu (Connor) wrote:

<...>

> 在 2022/1/26 21:10, Ferruh Yigit 写道:
>> 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>
> 
> Acked-by: Min Hu (Connor) <humin29@huawei.com>
> 

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2022-02-01 11:45 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
2022-01-27  9:18 ` Min Hu (Connor)
2022-02-01 11:44   ` Ferruh Yigit [this message]

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=b4fc47a6-e5be-3e34-7233-0a1b0020ab07@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=arybchenko@solarflare.com \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=ivan.ilchenko@oktetlabs.ru \
    --cc=stable@dpdk.org \
    --cc=yux.jiang@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).