Re: [RFC net-next v2 1/2] devlink: add whole device devlink instance

From
Jacob Keller <jacob.e.keller@intel.com>
Date
2025-02-24 22:10:22
Also in
intel-wired-lan, lkml
Reply to
Jiri Pirko, 2025-02-24

On 2/24/2025 5:03 AM, Jiri Pirko wrote:
Fri, Feb 21, 2025 at 02:45:12AM +0100, kuba@kernel.org wrote:
quoted
On Wed, 19 Feb 2025 17:32:54 +0100 Przemek Kitszel wrote:
quoted
Thanks to Wojciech Drewek for very nice naming of the devlink instance:
PF0:		pci/0000:00:18.0
whole-dev:	pci/0000:00:18
But I made this a param for now (driver is free to pass just "whole-dev").
Which only works nicely if you're talking about functions not full
separate links :) When I was thinking about it a while back my
intuition was that we should have a single instance, just accessible
under multiple names. But I'm not married to that direction if there
are problems with it.
I kind of agree. Like multiple channels to one entity, each labeled by a
different name (handle in devlink case).
This might actually also help alleviate some of the uAPI concerns too?
Since the original names would access the instance.
Thread (19 messages) 19 messages, 4 authors, last reply 2025-03-18
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help