From: Chas Williams <3chas3@gmail.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>
Cc: stable@dpdk.org, Hari Kumar Vemula <hari.kumarx.vemula@intel.com>,
Ivan Malov <ivan.malov@oktetlabs.ru>,
dev@dpdk.org
Subject: Re: [PATCH] net/bonding: fix descriptor limit reporting
Date: Mon, 17 Oct 2022 08:40:53 -0400 [thread overview]
Message-ID: <c213e5bb-bbec-7c73-14d1-4842f029410a@gmail.com> (raw)
In-Reply-To: <8c5c2c63-20de-c1a5-ff06-142bfbc49c47@oktetlabs.ru>
Acked-by: Chas Williams <3chas3@gmail.com>
On 10/17/22 04:40, Andrew Rybchenko wrote:
> Chas, Cornor, could you review the patch, please.
>
> Thanks,
> Andrew.
>
> On 9/11/22 15:19, Ivan Malov wrote:
>> Commit 5be3b40fea60 ("net/bonding: fix values of descriptor limits")
>> breaks reporting of "nb_min" and "nb_align" values obtained from
>> back-end devices' descriptor limits. This means that work done
>> by eth_bond_slave_inherit_desc_lim_first() as well as
>> eth_bond_slave_inherit_desc_lim_next() gets dismissed.
>>
>> Revert the offending commit and use proper workaround
>> for the test case mentioned in the said commit.
>>
>> Meanwhile, the test case itself might be poorly constructed.
>> It tries to run a bond with no back-end devices attached,
>> but, according to [1] ("Requirements / Limitations"),
>> at least one back-end device must be attached.
>>
>> [1] doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
>>
>> Fixes: 5be3b40fea60 ("net/bonding: fix values of descriptor limits")
>> 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 | 21 +++++++++++----------
>> 1 file changed, 11 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c
>> b/drivers/net/bonding/rte_eth_bond_pmd.c
>> index 3191158ca7..a5429f5e97 100644
>> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
>> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
>> @@ -2200,8 +2200,6 @@ bond_ethdev_info(struct rte_eth_dev *dev, struct
>> rte_eth_dev_info *dev_info)
>> uint16_t max_nb_rx_queues = UINT16_MAX;
>> uint16_t max_nb_tx_queues = UINT16_MAX;
>> - uint16_t max_rx_desc_lim = UINT16_MAX;
>> - uint16_t max_tx_desc_lim = UINT16_MAX;
>> dev_info->max_mac_addrs = BOND_MAX_MAC_ADDRS;
>> @@ -2235,12 +2233,6 @@ bond_ethdev_info(struct rte_eth_dev *dev,
>> struct rte_eth_dev_info *dev_info)
>> if (slave_info.max_tx_queues < max_nb_tx_queues)
>> max_nb_tx_queues = slave_info.max_tx_queues;
>> -
>> - if (slave_info.rx_desc_lim.nb_max < max_rx_desc_lim)
>> - max_rx_desc_lim = slave_info.rx_desc_lim.nb_max;
>> -
>> - if (slave_info.tx_desc_lim.nb_max < max_tx_desc_lim)
>> - max_tx_desc_lim = slave_info.tx_desc_lim.nb_max;
>> }
>> }
>> @@ -2252,8 +2244,10 @@ bond_ethdev_info(struct rte_eth_dev *dev,
>> struct rte_eth_dev_info *dev_info)
>> memcpy(&dev_info->default_txconf, &internals->default_txconf,
>> sizeof(dev_info->default_txconf));
>> - dev_info->rx_desc_lim.nb_max = max_rx_desc_lim;
>> - dev_info->tx_desc_lim.nb_max = max_tx_desc_lim;
>> + memcpy(&dev_info->rx_desc_lim, &internals->rx_desc_lim,
>> + sizeof(dev_info->rx_desc_lim));
>> + memcpy(&dev_info->tx_desc_lim, &internals->tx_desc_lim,
>> + sizeof(dev_info->tx_desc_lim));
>> /**
>> * If dedicated hw queues enabled for link bonding device in
>> LACP mode
>> @@ -3387,6 +3381,13 @@ bond_alloc(struct rte_vdev_device *dev, uint8_t
>> mode)
>> memset(&internals->rx_desc_lim, 0, sizeof(internals->rx_desc_lim));
>> memset(&internals->tx_desc_lim, 0, sizeof(internals->tx_desc_lim));
>> + /*
>> + * Do not restrict descriptor counts until
>> + * the first back-end device gets attached.
>> + */
>> + internals->rx_desc_lim.nb_max = UINT16_MAX;
>> + internals->tx_desc_lim.nb_max = UINT16_MAX;
>> +
>> memset(internals->active_slaves, 0,
>> sizeof(internals->active_slaves));
>> memset(internals->slaves, 0, sizeof(internals->slaves));
>
next prev parent reply other threads:[~2022-10-17 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 12:19 Ivan Malov
2022-10-17 8:40 ` Andrew Rybchenko
2022-10-17 12:40 ` Chas Williams [this message]
2022-10-17 14:08 ` 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=c213e5bb-bbec-7c73-14d1-4842f029410a@gmail.com \
--to=3chas3@gmail.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=hari.kumarx.vemula@intel.com \
--cc=humin29@huawei.com \
--cc=ivan.malov@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).