From: Carolina Jubran <cjubran@nvidia.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Tariq Toukan <tariqt@nvidia.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net 4/6] net/mlx5: Destroy vport QoS element when no configuration remains
Date: Sun, 17 Aug 2025 11:36:43 +0300 [thread overview]
Message-ID: <3a5673b7-47d2-4a59-a515-95b396364994@nvidia.com> (raw)
In-Reply-To: <51908ab2-6184-405a-b723-8b030267e7c1@intel.com>
On 14/08/2025 12:55, Przemek Kitszel wrote:
> On 8/13/25 16:31, Tariq Toukan wrote:
>> From: Carolina Jubran <cjubran@nvidia.com>
>>
>> If a VF has been configured and the user later clears all QoS settings,
>> the vport element remains in the firmware QoS tree. This leads to
>> inconsistent behavior compared to VFs that were never configured, since
>> the FW assumes that unconfigured VFs are outside the QoS hierarchy.
>> As a result, the bandwidth share across VFs may differ, even though
>> none of them appear to have any configuration.
>>
>> Align the driver behavior with the FW expectation by destroying the
>> vport QoS element when all configurations are removed.
>>
>> Fixes: c9497c98901c ("net/mlx5: Add support for setting VF min rate")
>> Fixes: cf7e73770d1b ("net/mlx5: Manage TC arbiter nodes and implement
>> full support for tc-bw")
>> Signed-off-by: Carolina Jubran <cjubran@nvidia.com>
>> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com>
>> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
>> ---
>> .../net/ethernet/mellanox/mlx5/core/esw/qos.c | 54 +++++++++++++++++--
>> 1 file changed, 51 insertions(+), 3 deletions(-)
>
>
>> +static bool esw_vport_qos_check_and_disable(struct mlx5_vport *vport,
>> + struct devlink_rate *parent,
>> + u64 tx_max, u64 tx_share,
>> + u32 *tc_bw)
>> +{
>> + struct mlx5_eswitch *esw = vport->dev->priv.eswitch;
>> +
>> + if (parent || tx_max || tx_share || !esw_qos_tc_bw_disabled(tc_bw))
>> + return false;
>> +
>> + esw_qos_lock(esw);
>> + mlx5_esw_qos_vport_disable_locked(vport);
>> + esw_qos_unlock(esw);
>> +
>> + return true;
>> +}
>> +
>> int mlx5_esw_qos_init(struct mlx5_eswitch *esw)
>> {
>> if (esw->qos.domain)
>> @@ -1703,6 +1731,11 @@ int
>> mlx5_esw_devlink_rate_leaf_tx_share_set(struct devlink_rate
>> *rate_leaf, void
>> if (!mlx5_esw_allowed(esw))
>> return -EPERM;
>> + if (esw_vport_qos_check_and_disable(vport, rate_leaf->parent,
>> + rate_leaf->tx_max, tx_share,
>> + rate_leaf->tc_bw))
>> + return 0;
>> +
>
> I would rather keep executing the code that "sets tx_share to 0 and
> propagates the info", and only then prune all-0 nodes.
> Same for other params (tx_max, ...)
>
> That would be less risky and more future-proof, and also would let your
> check&disable function to take less params.
>
> Finally, the name is poor, what about:?
> esw_vport_qos_prune_empty(vport, rate_leaf);
> (after applying my prev suggestion the above line will be at the
> bottom of function).
>
> Also a note, that if you apply the above, it would be also good to
> keep the "esw_qos_lock() just once" (as it is now)
>
Thanks for the review!
My initial thought was to reduce the amount of FW commands, but I agree
with your points.
Also, thanks for the name suggestion.
I’ll fix and send v2.
Carolina
>> err = esw_qos_devlink_rate_to_mbps(vport->dev, "tx_share",
>> &tx_share, extack);
>> if (err)
>> return err;
>> @@ -1724,6 +1757,11 @@ int
>> mlx5_esw_devlink_rate_leaf_tx_max_set(struct devlink_rate *rate_leaf,
>> void *
>> if (!mlx5_esw_allowed(esw))
>> return -EPERM;
>> + if (esw_vport_qos_check_and_disable(vport, rate_leaf->parent,
>> tx_max,
>> + rate_leaf->tx_share,
>> + rate_leaf->tc_bw))
>> + return 0;
>> +
>> err = esw_qos_devlink_rate_to_mbps(vport->dev, "tx_max",
>> &tx_max, extack);
>> if (err)
>> return err;
>> @@ -1749,6 +1787,11 @@ int mlx5_esw_devlink_rate_leaf_tc_bw_set(struct
>> devlink_rate *rate_leaf,
>> if (!mlx5_esw_allowed(esw))
>> return -EPERM;
>> + if (esw_vport_qos_check_and_disable(vport, rate_leaf->parent,
>> + rate_leaf->tx_max,
>> + rate_leaf->tx_share, tc_bw))
>> + return 0;
>> +
>> disable = esw_qos_tc_bw_disabled(tc_bw);
>> esw_qos_lock(esw);
>> @@ -1930,6 +1973,11 @@ int
>> mlx5_esw_devlink_rate_leaf_parent_set(struct devlink_rate *devlink_rate,
>> struct mlx5_esw_sched_node *node;
>> struct mlx5_vport *vport = priv;
>> + if (esw_vport_qos_check_and_disable(vport, parent, devlink_rate-
>> >tx_max,
>> + devlink_rate->tx_share,
>> + devlink_rate->tc_bw))
>> + return 0;
>> +
>> if (!parent)
>> return mlx5_esw_qos_vport_update_parent(vport, NULL, extack);
>
next prev parent reply other threads:[~2025-08-17 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 14:31 [PATCH net 0/6] mlx5 misc fixes 2025-08-13 Tariq Toukan
2025-08-13 14:31 ` [PATCH net 1/6] net/mlx5: Base ECVF devlink port attrs from 0 Tariq Toukan
2025-08-13 14:31 ` [PATCH net 2/6] net/mlx5: Fix QoS reference leak in vport enable error path Tariq Toukan
2025-08-13 14:31 ` [PATCH net 3/6] net/mlx5: Restore missing scheduling node cleanup on vport enable failure Tariq Toukan
2025-08-13 14:31 ` [PATCH net 4/6] net/mlx5: Destroy vport QoS element when no configuration remains Tariq Toukan
2025-08-14 9:55 ` Przemek Kitszel
2025-08-17 8:36 ` Carolina Jubran [this message]
2025-08-13 14:31 ` [PATCH net 5/6] net/mlx5e: Preserve tc-bw during parent changes Tariq Toukan
2025-08-13 14:31 ` [PATCH net 6/6] net/mlx5e: Query FW for buffer ownership Tariq Toukan
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=3a5673b7-47d2-4a59-a515-95b396364994@nvidia.com \
--to=cjubran@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®