linux-kernel - Re: [PATCH net-next V4 02/14] documentation: networking: add shared devlink documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251204105737.551d1cc1@kernel.org>
Date: Thu, 4 Dec 2025 10:57:37 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Tariq Toukan <tariqt@...dia.com>, Eric Dumazet <edumazet@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>, Andrew Lunn <andrew+netdev@...n.ch>,
 "David S. Miller" <davem@...emloft.net>, Donald Hunter
 <donald.hunter@...il.com>, Jonathan Corbet <corbet@....net>, Saeed Mahameed
 <saeedm@...dia.com>, Leon Romanovsky <leon@...nel.org>, Mark Bloch
 <mbloch@...dia.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-rdma@...r.kernel.org, Gal Pressman
 <gal@...dia.com>, Moshe Shemesh <moshe@...dia.com>, Carolina Jubran
 <cjubran@...dia.com>, Cosmin Ratiu <cratiu@...dia.com>, Jiri Pirko
 <jiri@...dia.com>, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH net-next V4 02/14] documentation: networking: add shared
 devlink documentation

On Wed, 3 Dec 2025 11:36:13 +0100 Jiri Pirko wrote:
> >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.