From: Jason Gunthorpe <jgg@ziepe.ca>
To: Qing Huang <qing.huang@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
dledford@redhat.com, leon@kernel.org, gerald.gibson@oracle.com,
danielj@mellanox.com, sharon.s.liu@oracle.com
Subject: Re: [PATCH v2] IB/mlx5: avoid excessive warning msgs when creating VFs on 2nd port
Date: Thu, 26 Jul 2018 16:12:14 -0600 [thread overview]
Message-ID: <20180726221214.GA13670@ziepe.ca> (raw)
In-Reply-To: <20180723211508.7078-1-qing.huang@oracle.com>
On Mon, Jul 23, 2018 at 02:15:08PM -0700, Qing Huang wrote:
> When a CX5 device is configured in dual-port RoCE mode, after creating
> many VFs against port 1, creating the same number of VFs against port 2
> will flood kernel/syslog with something like
> "mlx5_*:mlx5_ib_bind_slave_port:4266:(pid 5269): port 2 already
> affiliated."
>
> So basically, when traversing mlx5_ib_dev_list, mlx5_ib_add_slave_port()
> repeatedly attempts to bind the new mpi structure to every device
> on the list until it finds an unbound device.
>
> Change the log level from warn to dbg to avoid log flooding as the warning
> should be harmless.
>
> Signed-off-by: Qing Huang <qing.huang@oracle.com>
> Reviewed-by: Daniel Jurgens <danielj@mellanox.com>
> ---
> v1 -> v2: change the log level instead
Applied to for-next
Thanks,
Jason
prev parent reply other threads:[~2018-07-26 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 21:15 [PATCH v2] IB/mlx5: avoid excessive warning msgs when creating VFs on 2nd port Qing Huang
2018-07-23 21:17 ` Daniel Jurgens
2018-07-26 22:12 ` Jason Gunthorpe [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=20180726221214.GA13670@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=danielj@mellanox.com \
--cc=dledford@redhat.com \
--cc=gerald.gibson@oracle.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=qing.huang@oracle.com \
--cc=sharon.s.liu@oracle.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