From: Kamal Heib <kamalheib1@gmail.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
Christian Benvenuti <benve@cisco.com>
Subject: Re: [PATCH for-rc] RDMA/usnic: Fix reported max_pkeys attribute
Date: Mon, 17 Aug 2020 01:04:40 +0300 [thread overview]
Message-ID: <20200816220440.GA820535@kheib-workstation> (raw)
In-Reply-To: <20200814165408.GU24045@ziepe.ca>
On Fri, Aug 14, 2020 at 01:54:08PM -0300, Jason Gunthorpe wrote:
> On Mon, Aug 10, 2020 at 11:19:18PM +0300, Kamal Heib wrote:
> > On Wed, Aug 05, 2020 at 07:17:42PM -0300, Jason Gunthorpe wrote:
> > > On Thu, Aug 06, 2020 at 12:00:51AM +0300, Kamal Heib wrote:
> > > > Make sure to report the right max_pkeys attribute value to indicate the
> > > > maximum number of partitions supported by the usnic device.
> > >
> > > Why does usnic support pkeys? This needs more explanation
> > >
> > > Jason
> >
> > Looks like the usnic provider is acting like the RoCE providers by returning
> > the default pkey when calling the query_pkey() callback, Do you think that
> > this needs to removed like what was done for iWarp providers?
> >
> > int usnic_ib_query_pkey(struct ib_device *ibdev, u8 port, u16 index,
> > u16 *pkey)
> > {
> > if (index > 0)
> > return -EINVAL;
> >
> > *pkey = 0xffff;
> > return 0;
> > }
>
> You'd have to check the libfabric provider to see if it cares or not
>
> Jason
Looks like the usnic provider under libfabric doesn't care about
pkey/query_pkey, I'll prepare a patch that will remove the query_pkey()
callback.
kheib master ~ git upstream libfabric git grep -n query_pkey prov/usnic/
kheib master ~ git upstream libfabric git grep -n pkey prov/usnic/
kheib master ~ git upstream libfabric
Thanks,
Kamal
prev parent reply other threads:[~2020-08-16 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 21:00 [PATCH for-rc] RDMA/usnic: Fix reported max_pkeys attribute Kamal Heib
2020-08-05 22:17 ` Jason Gunthorpe
2020-08-10 20:19 ` Kamal Heib
2020-08-14 16:54 ` Jason Gunthorpe
2020-08-16 22:04 ` Kamal Heib [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=20200816220440.GA820535@kheib-workstation \
--to=kamalheib1@gmail.com \
--cc=benve@cisco.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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