From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Or Har-Toov <ohartoov@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
Edward Srouji <edwards@nvidia.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Shay Drory <shayd@nvidia.com>
Subject: Re: [PATCH rdma-next] RDMA/mlx5: Remove warn on missing representor in query_port_speed
Date: Tue, 01 Sep 2026 09:28:26 -0400 [thread overview]
Message-ID: <178826930675.1340197.11507310539690943779.b4-ty@kernel.org> (raw)
In-Reply-To: <20260811-remove-warn-on-miss-rep-v1-1-eccf399bc6af@nvidia.com>
On Tue, 11 Aug 2026 19:25:57 +0300, Edward Srouji wrote:
> The representor ib_device's phys_port_cnt is set to the total vport
> count when the uplink vport rep loads. Individual port[i].rep entries
> are populated only as each VF/SF vport rep registers. A NULL .rep for
> a given port index is therefore expected while VF reps are still
> loading or haven't been enabled yet.
>
> Tools like ibstat and ibv_devinfo iterate over all ports of all RDMA
> devices. Some ports may not have an eswitch representor, causing
> repeated dmesg warnings when these tools run without a device argument.
> This causes dmesg to be flooded with this message on every ibstat
> invocation.
>
> [...]
Applied, thanks!
[1/1] RDMA/mlx5: Remove warn on missing representor in query_port_speed
https://git.kernel.org/rdma/rdma/c/2be77295316c2d
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-09-01 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 16:25 Edward Srouji
2026-09-01 13:28 ` Leon Romanovsky [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=178826930675.1340197.11507310539690943779.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=edwards@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=shayd@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
all inboxes | Powered by JetHome®