Thread (22 messages) 22 messages, 4 authors, 2025-11-25

Re: [PATCH net-next 05/14] devlink: Decouple rate storage from associated devlink object

From: Jiri Pirko <jiri@resnulli.us>
Date: 2025-11-20 14:55:19
Also in: linux-doc, linux-rdma, lkml

Thu, Nov 20, 2025 at 02:09:17PM +0100, tariqt@nvidia.com wrote:
From: Cosmin Ratiu <redacted>

Devlink rate leafs and nodes were stored in their respective devlink
objects pointed to by devlink_rate->devlink.

This patch removes that association by introducing the concept of
'rate node devlink', which is where all rates that could link to each
other are stored. For now this is the same as devlink_rate->devlink.

After this patch, the devlink rates stored in this devlink instance
could potentially be from multiple other devlink instances. So all rate
node manipulation code was updated to:
- correctly compare the actual devlink object during iteration.
- maybe acquire additional locks (noop for now).

Signed-off-by: Cosmin Ratiu <redacted>
Reviewed-by: Carolina Jubran <redacted>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Reviewed-by: Jiri Pirko <redacted>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help