From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Chas Williams <3chas3@gmail.com>,
stable@dpdk.org, Declan Doherty <declan.doherty@intel.com>,
Matan Azrad <matan@mellanox.com>,
dev@dpdk.org
Subject: Re: [PATCH] net/bonding: fix flow flush order on bonded device close
Date: Wed, 19 Oct 2022 14:27:34 +0300 (MSK) [thread overview]
Message-ID: <daf1409f-1ff5-8239-d553-eb275ceeec82@oktetlabs.ru> (raw)
In-Reply-To: <6bf67a5b-6171-07cd-bd1a-6d6feb642487@oktetlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
Hi Chas, Andrew,
On Wed, 19 Oct 2022, Andrew Rybchenko wrote:
> On 10/17/22 15:34, Chas Williams wrote:
>> This appears to be correct, but it needs to be coordinated with the
>> proposed changes in net/bonding: make bonded device configure method
>> re-entrant
Needs to be coordinated - in which way? Are you looking to reorder
the patches? If yes, v2 should be OK with this regard.
>
> Ivan, could you comment and send rebased v2 version anyway.
Please see
https://patches.dpdk.org/project/dpdk/patch/20221019111805.1070381-1-ivan.malov@oktetlabs.ru/
.
>
>>
>>
>> On 10/17/22 04:41, Andrew Rybchenko wrote:
>>> Chas, Cornor, could you review the patch, please.
>>>
>>> Thanks,
>>> Andrew.
>>>
>>> On 9/11/22 15:22, Ivan Malov wrote:
>>>> The current code first removes all back-end devices of
>>>> the bonded device and then invokes flush operation to
>>>> remove flows in such back-end devices, which makes no
>>>> sense. Fix that by re-ordering the steps accordingly.
>>>>
>>>> Fixes: 49dad9028e2a ("net/bonding: support flow API")
>>>> Cc: stable@dpdk.org
>>>>
>>>> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
>>>> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>>>> ---
>>>> drivers/net/bonding/rte_eth_bond_pmd.c | 5 ++++-
>>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c
>>>> b/drivers/net/bonding/rte_eth_bond_pmd.c
>>>> index a5429f5e97..d01c954296 100644
>>>> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
>>>> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
>>>> @@ -2155,6 +2155,10 @@ bond_ethdev_close(struct rte_eth_dev *dev)
>>>> return 0;
>>>> RTE_BOND_LOG(INFO, "Closing bonded device %s", dev->device->name);
>>>> +
>>>> + /* Flush flows in all back-end devices before removing them */
>>>> + bond_flow_ops.flush(dev, &ferror);
>>>> +
>>>> while (internals->slave_count != skipped) {
>>>> uint16_t port_id = internals->slaves[skipped].port_id;
>>>> @@ -2172,7 +2176,6 @@ bond_ethdev_close(struct rte_eth_dev *dev)
>>>> skipped++;
>>>> }
>>>> }
>>>> - bond_flow_ops.flush(dev, &ferror);
>>>> bond_ethdev_free_queues(dev);
>>>> rte_bitmap_reset(internals->vlan_filter_bmp);
>>>> rte_bitmap_free(internals->vlan_filter_bmp);
>>>
>
>
next prev parent reply other threads:[~2022-10-19 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 12:22 Ivan Malov
2022-10-17 8:41 ` Andrew Rybchenko
2022-10-17 12:34 ` Chas Williams
2022-10-19 10:29 ` Andrew Rybchenko
2022-10-19 11:27 ` Ivan Malov [this message]
2022-10-19 11:18 ` [PATCH v2] " Ivan Malov
2022-10-20 6:34 ` Andrew Rybchenko
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=daf1409f-1ff5-8239-d553-eb275ceeec82@oktetlabs.ru \
--to=ivan.malov@oktetlabs.ru \
--cc=3chas3@gmail.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chas3@att.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=matan@mellanox.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).