Re: [PATCH net-next V4 02/14] documentation: networking: add shared devlink documentation
From: Jakub Kicinski <kuba@kernel.org>
Date: 2025-12-04 18:57:39
Also in:
linux-doc, linux-rdma, lkml
From: Jakub Kicinski <kuba@kernel.org>
Date: 2025-12-04 18:57:39
Also in:
linux-doc, linux-rdma, lkml
On Wed, 3 Dec 2025 11:36:13 +0100 Jiri Pirko wrote:
quoted
To be clear -- I understand how you're laying things out. My point is not about that. My question is how can user make intuitive sense of this mess of random object floating around. Every SW engineering problem can be solved by another layer of abstraction, that's not the challenge. The challenge is to design those layers so that they make intuitive sense (to people who don't spend their life programming against mlx FW interfaces).Well, this really has no relation to mlx FW interfaces. It is a generic issue of having multiple PFs backed by 1 physical device sharing resources. How to make things more intuitive, I don't know :/ Any suggestion?
We're talking in circles. Having a single devlink instance for the "1 physical device" is far more intuitive than stringing together ports from two devlink instances by using a third instance.