From: Jakub Kicinski <kuba@kernel•org>
To: Louis Peens <louis.peens@corigine•com>
Cc: David Miller <davem@davemloft•net>,
Paolo Abeni <pabeni@redhat•com>,
Simon Horman <simon.horman@corigine•com>,
Yinjun Zhang <yinjun.zhang@corigine•com>,
Tianyu Yuan <tianyu.yuan@corigine•com>,
netdev@vger•kernel.org, oss-drivers@corigine•com
Subject: Re: [PATCH net-next v2 00/13] nfp: add support for multi-pf configuration
Date: Thu, 17 Aug 2023 19:22:05 -0700 [thread overview]
Message-ID: <20230817192205.599f108b@kernel.org> (raw)
In-Reply-To: <20230816143912.34540-1-louis.peens@corigine.com>
On Wed, 16 Aug 2023 16:38:59 +0200 Louis Peens wrote:
> As part of v1 there was also some partially finished discussion about
> devlink allowing to bind to multiple bus devices. This series creates a
> devlink instance per PF, and the comment was asking if this should maybe
> change to be a single instance, since it is still a single device. For
> the moment we feel that this is a parallel issue to this specific
> series, as it seems to be already implemented this way in other places,
> and this series would be matching that.
>
> We are curious about this idea though, as it does seem to make sense if
> the original devlink idea was that it should have a one-to-one
> correspondence per ASIC. Not sure where one would start with this
> though, on first glance it looks like the assumption that devlink is
> only connected to a single bus device is embedded quite deep. This
> probably needs commenting/discussion with somebody that has pretty good
> knowledge of devlink core.
How do you suggest we move forward? This is a community project after
all, _someone_ has to start the discussion and then write the code.
next prev parent reply other threads:[~2023-08-18 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:38 [PATCH net-next v2 00/13] nfp: add support for multi-pf configuration Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 01/13] nsp: generate nsp command with variable nsp major version Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 02/13] nfp: bump the nsp major version to support multi-PF Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 03/13] nfp: change application firmware loading flow in multi-PF setup Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 04/13] nfp: don't skip firmware loading when it's pxe firmware in running Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 05/13] io-64-nonatomic: truncate bits explicitly to avoid warning Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 06/13] nfp: introduce keepalive mechanism for multi-PF setup Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 07/13] nfp: avoid reclaiming resource mutex by mistake Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 08/13] nfp: redefine PF id used to format symbols Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 09/13] nfp: apply one port per PF for multi-PF setup Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 10/13] nfp: enable multi-PF in application firmware if supported Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 11/13] nfp: configure VF total count for each PF Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 12/13] nfp: configure VF split info into application firmware Louis Peens
2023-08-16 14:39 ` [PATCH net-next v2 13/13] nfp: use absolute vf id for multi-PF case Louis Peens
2023-08-18 2:22 ` Jakub Kicinski [this message]
2023-08-18 7:03 ` [PATCH net-next v2 00/13] nfp: add support for multi-pf configuration Louis Peens
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=20230817192205.599f108b@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=louis.peens@corigine$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oss-drivers@corigine$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
--cc=tianyu.yuan@corigine$(echo .)com \
--cc=yinjun.zhang@corigine$(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