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: Thu, 24 Apr 2025 15:06:29 -0700 [thread overview]
Message-ID: <20250424150629.7fbf2d3b@kernel.org> (raw)
In-Reply-To: <3kjuqbqtgfvklja3hmz55uh3pmlzruynih3lfainmnwzsog4hz@x7x74s2c36vx>
On Thu, 24 Apr 2025 11:42:09 +0200 Jiri Pirko wrote:
> This you see on the PF that is managing the eswitch. This devlink port
> is a representor of another PF, let's call it PFx. PFx may or may not be
> on a different host. It's a link from PF managed eswitch to PFx.
>
> So you have 2 PFs that are in hierarchy (one is on downlink of another),
> each on different host.
>
> To find out how these 2 are connected together, you need to know some
> identification, on both sides. On PF side, that is port.function.uid the
> patchset mentioned above introduces. On PFx, the same value is listed
> under devlink info, which is what my patch we are discussing here is
> adding.
Still not clear, sorry, can you show a diagram?
"Downsteam" makes me think the NIC device itself is a PCIe switch?
next prev parent reply other threads:[~2025-04-24 22:06 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
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 [this message]
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=20250424150629.7fbf2d3b@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.