From: Jacob Keller <jacob.e.keller@intel.com>
To: Jiri Pirko <jiri@resnulli.us>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Cosmin Ratiu <cratiu@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, <netdev@vger.kernel.org>,
Konrad Knitter <konrad.knitter@intel.com>, <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
<linux-kernel@vger.kernel.org>,
ITP Upstream <nxne.cnse.osdt.itp.upstreaming@intel.com>,
Carolina Jubran <cjubran@nvidia.com>
Subject: Re: [Intel-wired-lan] [RFC net-next v2 1/2] devlink: add whole device devlink instance
Date: Mon, 24 Feb 2025 14:12:29 -0800 [thread overview]
Message-ID: <b0857058-98bd-4de5-8e8b-e1e52d66bfe9@intel.com> (raw)
In-Reply-To: <ybrtz77i3hbxdwau4k55xn5brsnrtyomg6u65eyqm4fh7nsnob@arqyloer2l5z>
On 2/24/2025 8:14 AM, Jiri Pirko wrote:
>
> The shared parent entity for PFs (and other Fs) is always reference
> counted, first creates, last removes. I feel like this is something
> missing in PCI spec. If such beast would exist, very easy to implement
> this in devlink. We have all we need in place already.
>
>
This is basically what I was thinking too. It does feel like it fits in
the PCI layer better than in the devlink layer.. but Przemek also
mentioned the following from reading the other lists:
>
> I get that the general sentiment is to "leave the complexities to the
> driver/other layers", but it was based on reading only limited amount
> of internal (non networking) mailing lists.
Which makes me think going the PCI route might be tricky. I am not sure
if there is another way to get that model without though...
There was also something I saw recently merge, faux_bus? Not sure if
that would be just as ugly as your other 3 options though...
WARNING: multiple messages have this Message-ID (diff)
From: Jacob Keller <jacob.e.keller@intel.com>
To: Jiri Pirko <jiri@resnulli.us>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Cosmin Ratiu <cratiu@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, <netdev@vger.kernel.org>,
Konrad Knitter <konrad.knitter@intel.com>, <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
<linux-kernel@vger.kernel.org>,
ITP Upstream <nxne.cnse.osdt.itp.upstreaming@intel.com>,
Carolina Jubran <cjubran@nvidia.com>
Subject: Re: [RFC net-next v2 1/2] devlink: add whole device devlink instance
Date: Mon, 24 Feb 2025 14:12:29 -0800 [thread overview]
Message-ID: <b0857058-98bd-4de5-8e8b-e1e52d66bfe9@intel.com> (raw)
In-Reply-To: <ybrtz77i3hbxdwau4k55xn5brsnrtyomg6u65eyqm4fh7nsnob@arqyloer2l5z>
On 2/24/2025 8:14 AM, Jiri Pirko wrote:
>
> The shared parent entity for PFs (and other Fs) is always reference
> counted, first creates, last removes. I feel like this is something
> missing in PCI spec. If such beast would exist, very easy to implement
> this in devlink. We have all we need in place already.
>
>
This is basically what I was thinking too. It does feel like it fits in
the PCI layer better than in the devlink layer.. but Przemek also
mentioned the following from reading the other lists:
>
> I get that the general sentiment is to "leave the complexities to the
> driver/other layers", but it was based on reading only limited amount
> of internal (non networking) mailing lists.
Which makes me think going the PCI route might be tricky. I am not sure
if there is another way to get that model without though...
There was also something I saw recently merge, faux_bus? Not sure if
that would be just as ugly as your other 3 options though...
next prev parent reply other threads:[~2025-02-24 22:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:32 [Intel-wired-lan] [RFC net-next v2 0/2] devlink: whole-device, resource .occ_set() Przemek Kitszel
2025-02-19 16:32 ` Przemek Kitszel
2025-02-19 16:32 ` [Intel-wired-lan] [RFC net-next v2 1/2] devlink: add whole device devlink instance Przemek Kitszel
2025-02-19 16:32 ` Przemek Kitszel
2025-02-19 22:11 ` [Intel-wired-lan] " Jacob Keller
2025-02-19 22:11 ` Jacob Keller
2025-02-21 1:45 ` [Intel-wired-lan] " Jakub Kicinski
2025-02-21 1:45 ` Jakub Kicinski
2025-02-21 22:50 ` [Intel-wired-lan] " Jacob Keller
2025-02-21 22:50 ` Jacob Keller
2025-02-24 10:15 ` [Intel-wired-lan] " Przemek Kitszel
2025-02-24 10:15 ` Przemek Kitszel
2025-02-24 13:03 ` [Intel-wired-lan] " Jiri Pirko
2025-02-24 13:03 ` Jiri Pirko
2025-02-24 22:09 ` [Intel-wired-lan] " Jacob Keller
2025-02-24 22:09 ` Jacob Keller
2025-02-24 16:14 ` [Intel-wired-lan] " Jiri Pirko
2025-02-24 16:14 ` Jiri Pirko
2025-02-24 22:12 ` Jacob Keller [this message]
2025-02-24 22:12 ` Jacob Keller
2025-02-25 11:30 ` [Intel-wired-lan] " Przemek Kitszel
2025-02-25 11:30 ` Przemek Kitszel
2025-02-25 14:35 ` [Intel-wired-lan] " Jiri Pirko
2025-02-25 14:35 ` Jiri Pirko
2025-02-25 15:40 ` [Intel-wired-lan] " Przemek Kitszel
2025-02-25 15:40 ` Przemek Kitszel
2025-02-25 18:16 ` [Intel-wired-lan] " Jacob Keller
2025-02-25 18:16 ` Jacob Keller
2025-02-26 14:48 ` [Intel-wired-lan] " Jiri Pirko
2025-02-26 14:48 ` Jiri Pirko
2025-02-26 15:06 ` [Intel-wired-lan] " Przemek Kitszel
2025-02-26 15:06 ` Przemek Kitszel
2025-02-26 15:25 ` [Intel-wired-lan] " Jiri Pirko
2025-02-26 15:25 ` Jiri Pirko
2025-03-18 15:42 ` [Intel-wired-lan] " Jiri Pirko
2025-03-18 15:42 ` Jiri Pirko
2025-02-19 16:32 ` [Intel-wired-lan] [RFC net-next v2 2/2] devlink: give user option to allocate resources Przemek Kitszel
2025-02-19 16:32 ` Przemek Kitszel
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=b0857058-98bd-4de5-8e8b-e1e52d66bfe9@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=konrad.knitter@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.