From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "humin (Q)" <humin29@huawei.com>,
Chaoyong He <chaoyong.he@corigine.com>,
dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Long Wu <long.wu@corigine.com>,
matan@mellanox.com, stable@dpdk.org
Subject: Re: [PATCH] net/bonding: fix destroy dedicated queues flow
Date: Tue, 20 Jun 2023 12:20:30 +0100 [thread overview]
Message-ID: <f38c1712-e107-af4d-a1ec-776f95ceb0c8@amd.com> (raw)
In-Reply-To: <78d00943-e942-9498-b1d1-ac92a4695919@huawei.com>
On 6/20/2023 4:02 AM, humin (Q) wrote:
> 在 2023/6/8 10:59, Chaoyong He 写道:
>> From: Long Wu <long.wu@corigine.com>
>>
>> Bonding port in mode 4 enables dedicated queues, we
>> will create a flow for this feature. So we need to
>> destroy this flow when we remove the member port.
>>
>> Furthermore if we don't destroy the flow that created
>> for dedicated queues when we remove the member port,
>> maybe we couldn't add the member port to a new bonding
>> port that needed dedicated queues.
>>
>> We add the destroy action in removing member port
>> function.
>>
>> Fixes: 49dad9028e2a ("net/bonding: support flow API")
>> Cc: matan@mellanox.com
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Long Wu <long.wu@corigine.com>
>> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
>> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
>>
>
> Acked-by: Min Hu (Connor) <humin29@huawei.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-20 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 2:59 Chaoyong He
2023-06-20 3:02 ` humin (Q)
2023-06-20 11:20 ` 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=f38c1712-e107-af4d-a1ec-776f95ceb0c8@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=long.wu@corigine.com \
--cc=matan@mellanox.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--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).