From: Jakub Kicinski <kuba@kernel.org>
To: Yinjun Zhang <yinjun.zhang@corigine.com>
Cc: Louis Peens <louis.peens@corigine.com>,
David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <simon.horman@corigine.com>,
Tianyu Yuan <tianyu.yuan@nephogine.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
oss-drivers <oss-drivers@corigine.com>
Subject: Re: [PATCH net-next 00/12] nfp: add support for multi-pf configuration
Date: Tue, 25 Jul 2023 11:59:33 -0700 [thread overview]
Message-ID: <20230725115933.29171e72@kernel.org> (raw)
In-Reply-To: <DM6PR13MB3705B9BEEEE2FF99A57F8559FC03A@DM6PR13MB3705.namprd13.prod.outlook.com>
On Tue, 25 Jul 2023 01:28:34 +0000 Yinjun Zhang wrote:
> On Tuesday, July 25, 2023 8:01 AM, Jakub Kicinski wrote:
> > On Mon, 24 Jul 2023 11:48:09 +0200 Louis Peens wrote:
> > > This patch series is introducing multiple PFs for multiple ports NIC
> > > assembled with NFP3800 chip. This is done since the NFP3800 can
> > > support up to 4 PFs, and is more in-line with the modern expectation
> > > that each port/netdev is associated with a unique PF.
> > >
> > > For compatibility concern with NFP4000/6000 cards, and older management
> > > firmware on NFP3800, multiple ports sharing single PF is still supported
> > > with this change. Whether it's multi-PF setup or single-PF setup is
> > > determined by management firmware, and driver will notify the
> > > application firmware of the setup so that both are well handled.
> >
> > So every PF will have its own devlink instance?
> > Can you show devlink dev info output?
>
> Yes, here it is:
> serial_number UKAAMDA2000-100122190023
> serial_number UKAAMDA2000-100122190023
Since it's clearly a single ASIC shouldn't it have a single devlink
instance?
next prev parent reply other threads:[~2023-07-25 18:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 9:48 [PATCH net-next 00/12] nfp: add support for multi-pf configuration Louis Peens
2023-07-24 9:48 ` [PATCH net-next 01/12] nsp: generate nsp command with variable nsp major version Louis Peens
2023-07-24 9:48 ` [PATCH net-next 02/12] nfp: bump the nsp major version to support multi-PF Louis Peens
2023-07-24 9:48 ` [PATCH net-next 03/12] nfp: change application firmware loading flow in multi-PF setup Louis Peens
2023-07-24 9:48 ` [PATCH net-next 04/12] nfp: don't skip firmware loading when it's pxe firmware in running Louis Peens
2023-07-24 9:48 ` [PATCH net-next 05/12] nfp: introduce keepalive mechanism for multi-PF setup Louis Peens
2023-07-29 20:20 ` kernel test robot
2023-07-30 4:51 ` Yinjun Zhang
2023-08-07 2:10 ` Yinjun Zhang
2023-07-24 9:48 ` [PATCH net-next 06/12] nfp: avoid reclaiming resource mutex by mistake Louis Peens
2023-07-24 9:48 ` [PATCH net-next 07/12] nfp: redefine PF id used to format symbols Louis Peens
2023-07-24 9:48 ` [PATCH net-next 08/12] nfp: apply one port per PF for multi-PF setup Louis Peens
2023-07-24 9:48 ` [PATCH net-next 09/12] nfp: enable multi-PF in application firmware if supported Louis Peens
2023-07-24 9:48 ` [PATCH net-next 10/12] nfp: configure VF total count for each PF Louis Peens
2023-07-24 9:48 ` [PATCH net-next 11/12] nfp: configure VF split info into application firmware Louis Peens
2023-07-24 9:48 ` [PATCH net-next 12/12] nfp: use absolute vf id for multi-PF case Louis Peens
2023-07-25 0:01 ` [PATCH net-next 00/12] nfp: add support for multi-pf configuration Jakub Kicinski
2023-07-25 1:28 ` Yinjun Zhang
2023-07-25 18:59 ` Jakub Kicinski [this message]
2023-07-26 2:00 ` Yinjun Zhang
2023-07-26 4:17 ` Jakub Kicinski
2023-07-26 7:28 ` Yinjun Zhang
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=20230725115933.29171e72@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=tianyu.yuan@nephogine.com \
--cc=yinjun.zhang@corigine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).