From: Jason Gunthorpe <jgg@nvidia.com>
To: "Håkon Bugge" <haakon.bugge@oracle.com>
Cc: Doug Ledford <dledford@redhat.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc] IB/cma: Fix false P_Key mismatch messages
Date: Mon, 10 May 2021 14:04:33 -0300 [thread overview]
Message-ID: <20210510170433.GA1104569@nvidia.com> (raw)
In-Reply-To: <1620219241-24979-1-git-send-email-haakon.bugge@oracle.com>
On Wed, May 05, 2021 at 02:54:01PM +0200, Håkon Bugge wrote:
> There are three conditions that must be fulfilled in order to consider
> a partition match. Those are:
>
> 1. Both P_Keys must valid
> 2. At least one must be a full member
> 3. The partitions (lower 15 bits) must match
>
> In system employing both limited and full membership ports, we see
> these false warning messages:
>
> RDMA CMA: got different BTH P_Key (0x2a00) and primary path P_Key (0xaa00)
> RDMA CMA: in the future this may cause the request to be dropped
>
> even though the partition is the same.
>
> See IBTA 10.9.1.2 Special P_Keys and 10.9.3 Partition Key Matching for
> a reference.
>
> Fixes: 84424a7fc793 ("IB/cma: Print warning on different inner and header P_Keys")
> Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
> ---
> drivers/infiniband/core/cma.c | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
What is this trying to fix?
IMHO it is a bug on the sender side to send GMPs to use a pkey that
doesn't exactly match the data path pkey.
Jason
next prev parent reply other threads:[~2021-05-10 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 12:54 [PATCH for-rc] IB/cma: Fix false P_Key mismatch messages Håkon Bugge
2021-05-10 17:04 ` Jason Gunthorpe [this message]
2021-05-10 18:52 ` Haakon Bugge
2021-05-10 19:12 ` Jason Gunthorpe
2021-06-29 13:45 ` Haakon Bugge
2021-07-05 16:26 ` Jason Gunthorpe
2021-07-05 16:59 ` Haakon Bugge
2021-07-08 15:59 ` Haakon Bugge
2021-07-08 18:52 ` Jason Gunthorpe
2021-07-09 16:45 ` Haakon Bugge
2021-07-09 16:56 ` Jason Gunthorpe
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=20210510170433.GA1104569@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-rdma@vger.kernel.org \
/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).