From: Raslan Darawsheh <rasland@nvidia.com>
To: "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Xueming Li <xuemingl@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] net/mlx5: support no host PF configuration
Date: Mon, 28 Oct 2024 13:12:34 +0000 [thread overview]
Message-ID: <CH3PR12MB84608130AB17DB59F60C1CD6CF4A2@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231011064153.46486-1-jiaweiw@nvidia.com>
Hi,
From: Jiawei(Jonny) Wang <jiaweiw@nvidia.com>
Sent: Wednesday, October 11, 2023 9:41 AM
To: Suanming Mou; Xueming(Steven) Li; Slava Ovsiienko
Cc: dev@dpdk.org; Raslan Darawsheh
Subject: [PATCH] net/mlx5: support no host PF configuration
From: Xueming Li <xuemingl@nvidia.com>
In BlueField, a new firmware configuration option NUM_OF_PF=0 disables
PF on the x86 host side, no HPF on the ARM side, and the only RDMA port
on the ARM side is the bonding device(PF0). A device probe with devargs
of representor=pf[0-1]vf[...] will probe PF0 and PF1 one by one, and
it's possible that PF1 device scan results in no switch ports.
This patch supports the new configuration by allowing a PF scan with
empty switch ports.
Signed-off-by: Xueming Li <xuemingl@nvidia.com>
Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2024-10-28 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 6:41 Jiawei Wang
2024-09-27 7:11 ` Bing Zhao
2024-10-28 9:35 ` Dariusz Sosnowski
2024-10-07 18:09 ` Stephen Hemminger
2024-10-28 13:12 ` Raslan Darawsheh [this message]
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=CH3PR12MB84608130AB17DB59F60C1CD6CF4A2@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=jiaweiw@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@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 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).