All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiawei Wang <jiaweiw@nvidia.com>
Cc: <suanmingm@nvidia.com>, <xuemingl@nvidia.com>,
	<viacheslavo@nvidia.com>, <dev@dpdk.org>, <rasland@nvidia.com>
Subject: Re: [PATCH] net/mlx5: support no host PF configuration
Date: Mon, 7 Oct 2024 11:09:37 -0700	[thread overview]
Message-ID: <20241007110937.14ca3480@hermes.local> (raw)
In-Reply-To: <20231011064153.46486-1-jiaweiw@nvidia.com>

On Wed, 11 Oct 2023 09:41:53 +0300
Jiawei Wang <jiaweiw@nvidia.com> wrote:

> 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>

Not sure why it never got merged but looks fine.

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  parent reply	other threads:[~2024-10-07 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  6:41 [PATCH] net/mlx5: support no host PF configuration Jiawei Wang
2024-09-27  7:11 ` Bing Zhao
2024-10-28  9:35   ` Dariusz Sosnowski
2024-10-07 18:09 ` Stephen Hemminger [this message]
2024-10-28 13:12 ` Raslan Darawsheh

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=20241007110937.14ca3480@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jiaweiw@nvidia.com \
    --cc=rasland@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 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.