Thread (23 messages) 23 messages, 4 authors, 2025-03-05

Re: [PATCH net-next 03/10] devlink: Serialize access to rate domains

flat view

From: Jakub Kicinski <kuba@kernel.org>
Date: 2025-02-26 01:40:07
Also in: linux-doc, linux-rdma, lkml

On Tue, 25 Feb 2025 14:36:07 +0100 Jiri Pirko wrote:
quoted
The problem comes from having a devlink instance per function /
port rather than for the ASIC. Spawn a single instance and the
problem will go away 🤷️  
Yeah, we currently have VF devlink ports created under PF devlink instance.
That is aligned with PCI geometry. If we have a single per-ASIC parent
devlink, this does not change and we still need to configure cross
PF devlink instances.
Why would there still be PF instances? I'm not suggesting that you
create a hierarchy of instances.
The only benefit I see is that we don't need rate domain, but
we can use parent devlink instance lock instead. The locking ordering
might be a bit tricky to fix though.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help