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, horms@kernel•org, donald.hunter@gmail•com,
corbet@lwn•net, skhan@linuxfoundation•org, saeedm@nvidia•com,
leon@kernel•org, tariqt@nvidia•com, mbloch@nvidia•com,
przemyslaw.kitszel@intel•com, mschmidt@redhat•com,
andrew+netdev@lunn•ch, rostedt@goodmis•org, mhiramat@kernel•org,
mathieu.desnoyers@efficios•com, chuck.lever@oracle•com,
matttbe@kernel•org, cjubran@nvidia•com, daniel.zahka@gmail•com,
linux-doc@vger•kernel.org, linux-rdma@vger•kernel.org,
linux-trace-kernel@vger•kernel.org
Subject: Re: [PATCH net-next v2 09/10] documentation: networking: add shared devlink documentation
Date: Sat, 28 Feb 2026 15:05:58 -0800 [thread overview]
Message-ID: <20260228150558.46f3be36@kernel.org> (raw)
In-Reply-To: <20260225133422.290965-10-jiri@resnulli.us>
On Wed, 25 Feb 2026 14:34:21 +0100 Jiri Pirko wrote:
> +Shared devlink instances allow multiple physical functions (PFs) on the same
> +chip to share an additional devlink instance for chip-wide operations. This
> +is implemented within individual drivers alongside the individual PF devlink
> +instances, not replacing them.
Sounds like you want to preclude what was the goal in the discussion
with Przemek you quoted - a shared instance _only_ case. We don't have
to implement it today, but I think it's an entirely sane direction.
So the docs should not state otherwise.
next prev parent reply other threads:[~2026-02-28 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 13:34 [PATCH net-next v2 00/10] devlink: introduce shared devlink instance for PFs on same chip Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 01/10] devlink: expose devlink instance index over netlink Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 02/10] devlink: store bus_name and dev_name pointers in struct devlink Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 03/10] devlink: avoid extra iterations when found devlink is not registered Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 04/10] devlink: allow to use devlink index as a command handle Jiri Pirko
2026-02-28 22:48 ` Jakub Kicinski
2026-03-02 10:23 ` Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 05/10] devlink: support index-based lookup via bus_name/dev_name handle Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 06/10] devlink: add devlink_dev_driver_name() helper and use it in trace events Jiri Pirko
2026-02-28 22:58 ` Jakub Kicinski
2026-03-02 9:44 ` Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 07/10] devlink: allow devlink instance allocation without a backing device Jiri Pirko
2026-02-28 23:01 ` Jakub Kicinski
2026-03-02 13:15 ` Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 08/10] devlink: introduce shared devlink instance for PFs on same chip Jiri Pirko
2026-02-28 23:03 ` Jakub Kicinski
2026-03-02 9:30 ` Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 09/10] documentation: networking: add shared devlink documentation Jiri Pirko
2026-02-28 23:05 ` Jakub Kicinski [this message]
2026-03-02 9:09 ` Jiri Pirko
2026-02-25 13:34 ` [PATCH net-next v2 10/10] net/mlx5: Add a shared devlink instance for PFs on same chip 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=20260228150558.46f3be36@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=chuck.lever@oracle$(echo .)com \
--cc=cjubran@nvidia$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=daniel.zahka@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jiri@resnulli$(echo .)us \
--cc=leon@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-trace-kernel@vger$(echo .)kernel.org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=matttbe@kernel$(echo .)org \
--cc=mbloch@nvidia$(echo .)com \
--cc=mhiramat@kernel$(echo .)org \
--cc=mschmidt@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=saeedm@nvidia$(echo .)com \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox