[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FDEBA43A-C98F-4E2B-A8F3-CA809FBAD479@oracle.com>
Date: Wed, 16 May 2018 20:14:50 +0200
From: Håkon Bugge <haakon.bugge@...cle.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: Doug Ledford <dledford@...hat.com>,
Don Hiatt <don.hiatt@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Sean Hefty <sean.hefty@...el.com>,
OFED mailing list <linux-rdma@...r.kernel.org>,
linux-kernel@...r.kernel.org,
Hal Rosenstock <hal@....mellanox.co.il>
Subject: Re: [PATCH IB/core 2/2] IB/cm: Send authentic pkey in REQ msg and
check eligibility of the pkeys
> On 16 May 2018, at 20:01, Jason Gunthorpe <jgg@...pe.ca> wrote:
>
> On Wed, May 16, 2018 at 07:46:10PM +0200, Håkon Bugge wrote:
>
>> OK. Lets take one example. The pkey table contains 0xFFFF, 0x8001,
>> 0x0001.
>>
>> The wce.pkey_index is 1 (i.e., pointing to 0x8001). Now, tell me, was
>> BTH.PKey 0x8001 (matches 0x8001) or was it 0x0001 (also matching
>> 0x8001) ?
>
> As far as the Linux core is concerned, it must have been 0x8001,
> because the only way the pkey_index feature works properly is if
> exact-match takes precedence over in-exact match.
And now if the table only contains 0xFFFF, 0x8001, how do you tell?
Håkon
Powered by blists - more mailing lists