[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250425134529.549f2cda@kernel.org>
Date: Fri, 25 Apr 2025 13:45:29 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, tariqt@...dia.com, andrew+netdev@...n.ch,
horms@...nel.org, donald.hunter@...il.com,
kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH net-next v3 2/3] devlink: add function unique identifier
to devlink dev info
On Fri, 25 Apr 2025 09:27:19 +0200 Jiri Pirko wrote:
> info_fuid is the devlink info function.uid I'm introducing.
> the "fuid" under port is the port function uid attr from the RFC
> patchset.
>
> Is it clearer now? Should I extend the diagram by something you miss?
Yes, it is clear. The eswitch side makes sense.
You just need to find a better place to expose the client side.
Powered by blists - more mailing lists