DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@oktetlabs.ru>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	dev@dpdk.org, Chas Williams <chas3@att.com>,
	Chas Williams <3chas3@gmail.com>,
	"Min Hu (Connor)" <humin29@huawei.com>
Subject: Re: [PATCH] net/bonding: make bonded device configure method re-entrant
Date: Tue, 18 Oct 2022 15:44:46 +0300	[thread overview]
Message-ID: <b7e9fd47-ef93-2a20-7689-f0e62d6ff0c9@oktetlabs.ru> (raw)
In-Reply-To: <ca3bf90e-c603-ba49-cf18-46179fff976e@gmail.com>

Ivan,

could you rebase the patch, please, and send a new version.

Thanks,
Andrew.

On 10/18/22 13:34, Chas Williams wrote:
> 
> 
> On 10/17/22 10:10, Andrew Rybchenko wrote:
>> On 10/17/22 15:32, Chas Williams wrote:
>>> This appears to be correct. A minor comment inline.
>>>
>>> On 10/17/22 04:42, Andrew Rybchenko wrote:
>>>> Chas, Cornor, could you review the patch, please.
>>>>
>>>> Thanks,
>>>> Andrew.
>>>>
>>>> On 9/11/22 15:24, Ivan Malov wrote:
>>>>> According to the documentation, rte_eth_dev_configure()
>>>>> can be invoked repeatedly while in stopped state.
>>>>> The current implementation in the bonding driver
>>>>> allows for that (technically), but the user sees
>>>>> warnings which say that back-end devices have
>>>>> already been harnessed. Re-factor the code
>>>>> to have cleanup before each (re-)configure.
>>>>>
>>>>> 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 | 27 
>>>>> ++++++++++++++++++--------
>>>>>   1 file changed, 19 insertions(+), 8 deletions(-)
>>>>>
>>>>> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c 
>>>>> b/drivers/net/bonding/rte_eth_bond_pmd.c
>>>>> index d01c954296..92a33b45bd 100644
>>>>> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
>>>>> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
>>>>> @@ -2143,18 +2143,13 @@ bond_ethdev_stop(struct rte_eth_dev *eth_dev)
>>>>>       return 0;
>>>>>   }
>>>>> -int
>>>>> -bond_ethdev_close(struct rte_eth_dev *dev)
>>>>> +static void
>>>>> +bond_ethdev_cfg_cleanup(struct rte_eth_dev *dev)
>>>>>   {
>>>>>       struct bond_dev_private *internals = dev->data->dev_private;
>>>>>       uint16_t bond_port_id = internals->port_id;
>>>>> -    int skipped = 0;
>>>>>       struct rte_flow_error ferror;
>>>>> -
>>>>> -    if (rte_eal_process_type() != RTE_PROC_PRIMARY)
>>>>> -        return 0;
>>>>> -
>>>>> -    RTE_BOND_LOG(INFO, "Closing bonded device %s", 
>>>>> dev->device->name);
>>>>> +    int skipped = 0;
>>>>>       /* Flush flows in all back-end devices before removing them */
>>>>>       bond_flow_ops.flush(dev, &ferror);
>>>>> @@ -2176,6 +2171,20 @@ bond_ethdev_close(struct rte_eth_dev *dev)
>>>>>               skipped++;
>>>>>           }
>>>>>       }
>>>>> +}
>>>>> +
>>>>> +int
>>>>> +bond_ethdev_close(struct rte_eth_dev *dev)
>>>>> +{
>>>>> +    struct bond_dev_private *internals = dev->data->dev_private;
>>>>> +
>>>>> +    if (rte_eal_process_type() != RTE_PROC_PRIMARY)
>>>>> +        return 0;
>>>>> +
>>>>> +    RTE_BOND_LOG(INFO, "Closing bonded device %s", 
>>>>> dev->device->name);
>>>>> +
>>>>> +    bond_ethdev_cfg_cleanup(dev);
>>>>> +
>>>>>       bond_ethdev_free_queues(dev);
>>>>>       rte_bitmap_reset(internals->vlan_filter_bmp);
>>>>>       rte_bitmap_free(internals->vlan_filter_bmp);
>>>>> @@ -3606,6 +3615,8 @@ bond_ethdev_configure(struct rte_eth_dev *dev)
>>>>>       unsigned i, j;
>>>>> +    bond_ethdev_cfg_cleanup(dev);
>>>>> +
>>>
>>> You might want a space after the variable declaration section. It makes
>>> it easier to read.
>>
>> I can fix it on applying. May I add your ack?
> 
> Acked-by: Chas Williams <3chas3@gmail.com>
> 
>>>
>>>>>       /*
>>>>>        * If RSS is enabled, fill table with default values and
>>>>>        * set key to the value specified in port RSS configuration.
>>>>
>>


  reply	other threads:[~2022-10-18 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 12:24 Ivan Malov
2022-10-17  8:42 ` Andrew Rybchenko
2022-10-17 12:32   ` Chas Williams
2022-10-17 14:10     ` Andrew Rybchenko
2022-10-18 10:34       ` Chas Williams
2022-10-18 12:44         ` Andrew Rybchenko [this message]
2022-10-18 19:45 ` [PATCH v2] " Ivan Malov
2022-10-19 10:26   ` Andrew Rybchenko
2022-11-01 10:56   ` Jiang, YuX
2022-11-01 16:33     ` Ivan Malov
2022-11-02  5:20       ` Jiang, YuX

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=b7e9fd47-ef93-2a20-7689-f0e62d6ff0c9@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=3chas3@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=ivan.malov@oktetlabs.ru \
    /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).