netdev - Re: [RFC PATCH v3 net-next] Documentation: devlink: Add devlink-sd

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240216184332.7b7fdba5@kernel.org>
Date: Fri, 16 Feb 2024 18:43:32 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: William Tu <witu@...dia.com>, Jacob Keller <jacob.e.keller@...el.com>,
 bodong@...dia.com, jiri@...dia.com, netdev@...r.kernel.org,
 saeedm@...dia.com, "aleksander.lobakin@...el.com"
 <aleksander.lobakin@...el.com>
Subject: Re: [RFC PATCH v3 net-next] Documentation: devlink: Add devlink-sd

On Fri, 16 Feb 2024 09:06:37 +0100 Jiri Pirko wrote:
> >We disagree how things should be modeled, sort of in principle.
> >I think it dates all the way back to your work on altnames.
> >We had the same conversation on DPLL :(
> >
> >I prefer to give objects unique IDs and a bunch of optional identifying
> >attributes, rather than trying to build some well organized hierarchy.
> >The hierarchy often becomes an unnecessary constraint.  
> 
> Sure, no problem on having floating objects with ids and attributes.
> But in case they relate to HW configuration, you need to somehow glue
> them to a device eventually. This is what I'm missing how you envision
> it. The lifetime of object and glue/unglue operations.

My desired lifetime is that the object (shared pool) gets created when
the first consumer (netdev) appears, and destroyed when the last one
disappears. Just like you can configure huge rings on a NIC while its
closed and that won't consume any memory, share pool shouldn't exist if
all its consumers are closed.

The tricky part is to come up with some way of saying that we want
multiple netdevs to not only use a shared pool, but which ones should
be sharing which pool, when the pools themselves don't get explicitly
created. Right?

Gluing to the device is easier, IIUC, once the pool is create we can
give it whatever attributes we want. devlink ID, bus/device, netdev,
IOMMU domain, anything.