From: Leon Romanovsky <leon@kernel.org>
To: "Tung, Chien Tin" <chien.tin.tung@intel.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
msanalla@nvidia.com
Subject: Re: Unable to create max_qp QPs on Mellanox ConnectX-4/6
Date: Tue, 19 Jul 2022 09:09:27 +0300 [thread overview]
Message-ID: <YtZKl8EflY3JkKQo@unreal> (raw)
In-Reply-To: <YtVNyKzvUBqfhNSY@unreal>
On Mon, Jul 18, 2022 at 03:10:48PM +0300, Leon Romanovsky wrote:
> On Mon, Jul 18, 2022 at 03:48:26AM +0000, Tung, Chien Tin wrote:
> > > On Thu, Jul 14, 2022 at 02:20:06PM +0000, Tung, Chien Tin wrote:
> > > > No one is interested in helping with Create QP issue with Mellanox
> > > controller?
> > >
> > > 1. Both Jason and I had personal issues that prevented from us to
> > > participate in linux-rdma ML.
> > Okay,, I don't know what that means but I won't dwell on it.
> >
> > > 2. max_qp is set by FW. Please contact NVidia support.
> > I sent this issue to the mailing list because with different kernel I get different
> > number with 5.18.5 creating 1/2 of QPs as RHEL 8.5/MOFED.
> > If you still think this is a FW issue, I can certainly take it up with support.
>
> We already started internal discussion about it. The observed behavior is
> a combination of FW issues together with very questionable kernel patch
> that tried to overcome them.
We are working to provide more comprehensive fix, but for now, you can
revert the following patch: 7f839965b2d7 ("net/mlx5: Update log_max_qp value to be 17 at most")
Thanks
>
> Thanks
prev parent reply other threads:[~2022-07-19 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 23:05 Unable to create max_qp QPs on Mellanox ConnectX-4/6 Tung, Chien Tin
2022-07-14 14:20 ` Tung, Chien Tin
2022-07-17 6:56 ` Leon Romanovsky
2022-07-18 3:48 ` Tung, Chien Tin
2022-07-18 7:16 ` Christoph Lameter
2022-07-18 12:10 ` Leon Romanovsky
2022-07-19 6:09 ` 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=YtZKl8EflY3JkKQo@unreal \
--to=leon@kernel.org \
--cc=chien.tin.tung@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=msanalla@nvidia.com \
--cc=saeedm@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.