From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, tariqt@nvidia.com, andrew+netdev@lunn.ch,
horms@kernel.org, donald.hunter@gmail.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH net-next v3 2/3] devlink: add function unique identifier to devlink dev info
Date: Tue, 22 Apr 2025 08:02:38 -0700 [thread overview]
Message-ID: <20250422080238.00cbc3dc@kernel.org> (raw)
In-Reply-To: <5abwoi3oh3jy7y65kybk42stfeu3a7bx4smx4bc5iueivusflj@qkttnjzlqzbl>
On Tue, 22 Apr 2025 11:18:23 +0200 Jiri Pirko wrote:
> Sat, Apr 19, 2025 at 02:20:15AM +0200, kuba@kernel.org wrote:
> >On Fri, 18 Apr 2025 12:15:01 +0200 Jiri Pirko wrote:
> >> Ports does not look suitable to me. In case of a function with multiple
> >> physical ports, would the same id be listed for multiple ports? What
> >> about representors?
> >
> >You're stuck in nVidia thinking. PF port != Ethernet port.
> >I said PF port.
>
> PF port representor represents the eswitch side of the link to the
> actual PF. The PF may or may not be on the same host.
>
> Ethernet port is physical port.
>
> Why this is nVidia thinking? How others understand it?
Because you don't have a PF port for local PF.
The information you want to convey is which of the PF ports is "local".
I believe we discussed this >5 years ago when I was trying to solve
this exact problem for the NFP.
The topology information belongs on the ports, not the main instance.
> >> This is a function propertly, therefore it makes sense to me to put it
> >> on devlink instance as devlink instance represents the function.
> >>
> >> Another patchset that is most probably follow-up on this by one of my
> >> colleagues will introduce fuid propertly on "devlink port function".
> >> By that and the info exposed by this patch, you would be able to identify
> >> which representor relates to which function cross-hosts. I think that
> >> your question is actually aiming at this, isn't it?
> >
> >Maybe it's time to pay off some technical debt instead of solving all
> >problems with yet another layer of new attributes :(
>
> What do you mean by this?
I keep saying that the devlink instance should represent the chip /
data processing pipeline.
> We need a way to identify port representor
> (PF/VF/SF, does not matter which) and the other side of the wire that
> may be on a different host. How else do you imagine to do the
> identification of these 2 sides?
next prev parent reply other threads:[~2025-04-22 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 21:41 [PATCH net-next v3 0/3] net/mlx5: Expose additional devlink dev info Jiri Pirko
2025-04-16 21:41 ` [PATCH net-next v3 1/3] net/mlx5: Expose serial numbers in devlink info Jiri Pirko
2025-04-16 21:41 ` [PATCH net-next v3 2/3] devlink: add function unique identifier to devlink dev info Jiri Pirko
2025-04-18 1:38 ` Jakub Kicinski
2025-04-18 10:15 ` Jiri Pirko
2025-04-19 0:20 ` Jakub Kicinski
2025-04-22 9:18 ` Jiri Pirko
2025-04-22 15:02 ` Jakub Kicinski [this message]
2025-04-23 11:23 ` Jiri Pirko
2025-04-23 22:17 ` Jakub Kicinski
2025-04-24 9:42 ` Jiri Pirko
2025-04-24 22:06 ` Jakub Kicinski
2025-04-25 7:27 ` Jiri Pirko
2025-04-25 20:45 ` Jakub Kicinski
2025-04-28 16:28 ` Jiri Pirko
2025-04-28 18:12 ` Jakub Kicinski
2025-04-29 7:16 ` Jiri Pirko
2025-04-16 21:41 ` [PATCH net-next v3 3/3] net/mlx5: Expose function UID in devlink info Jiri Pirko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250422080238.00cbc3dc@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.