linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kamal Heib <kamalheib1@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>
Subject: Re: [PATCH for-rc v1 0/4] RDMA/providers: Set max_pkey attribute
Date: Mon, 13 Jul 2020 11:22:03 +0300	[thread overview]
Message-ID: <20200713082203.GA793133@kheib-workstation> (raw)
In-Reply-To: <20200708232815.GP23676@nvidia.com>

On Wed, Jul 08, 2020 at 08:28:15PM -0300, Jason Gunthorpe wrote:
> On Tue, Jul 07, 2020 at 10:13:24PM +0300, Kamal Heib wrote:
> > On Tue, Jul 07, 2020 at 01:12:47PM -0300, Jason Gunthorpe wrote:
> > > On Mon, Jul 06, 2020 at 12:11:15PM +0300, Kamal Heib wrote:
> > > > This patch set makes sure to set the max_pkeys attribute to the providers
> > > > that aren't setting it or not setting it correctly.
> > > > 
> > > > v1: Drop the efa patch and target for-rc.
> > > > 
> > > > Kamal Heib (4):
> > > >   RDMA/siw: Set max_pkeys attribute
> > > >   RDMA/cxgb4: Set max_pkeys attribute
> > > >   RDMA/i40iw: Set max_pkeys attribute
> > > >   RDMA/usnic: Fix reported max_pkeys attribute
> > > 
> > > Why should iwarp have a 1 pkey value?
> > > 
> > > Jason
> > 
> > That is a good question :-)
> > 
> > My Idea in this patchset was to match between the reported pkey_tbl_len and
> > the max_pkeys attribute that the providers expose.
> > 
> > But after taking a deeper look now, I see that the RDMA core requires
> > from all providers to implement the query_pkey() callback, which before
> > [1] commit that will cause the provider driver not to load. For IB
> > providers the requirement make sense, also for RoCE providers, because
> > there is a requirement by the RoCE Spec to support the default PKey, For
> > iwarp providers, This doesn't make sense and I think that they decided to
> > do the same as RoCE and to avoid the driver load failure.
> > 
> > Probably, The requirement from the RDMA core needs to be changed and
> > the query_pkey() callback needs to be removed from the iwarp providers,
> > Thoughts?
> 
> Sure
> 
> But then the pkey table size is 0 right?
>

Correct, also there are required changes in the RDMA core:
1- Avoid exposing the pkeys sysfs entries for the iwarp providers.
2- Avoid allocating the pkey cache for the iwarp providers.

I've started this work and I hope to post patches in the upcoming days.

Thanks,
Kamal

> Jason

      reply	other threads:[~2020-07-13  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  9:11 [PATCH for-rc v1 0/4] RDMA/providers: Set max_pkey attribute Kamal Heib
2020-07-06  9:11 ` [PATCH for-rc v1 1/4] RDMA/siw: Set max_pkeys attribute Kamal Heib
2020-07-06  9:11 ` [PATCH for-rc v1 2/4] RDMA/cxgb4: " Kamal Heib
2020-07-06  9:11 ` [PATCH for-rc v1 3/4] RDMA/i40iw: " Kamal Heib
2020-07-06  9:11 ` [PATCH for-rc v1 4/4] RDMA/usnic: Fix reported " Kamal Heib
2020-07-06 14:57 ` [PATCH for-rc v1 1/4] RDMA/siw: Set " Bernard Metzler
2020-07-07 16:12 ` [PATCH for-rc v1 0/4] RDMA/providers: Set max_pkey attribute Jason Gunthorpe
2020-07-07 19:13   ` Kamal Heib
2020-07-08 23:28     ` Jason Gunthorpe
2020-07-13  8:22       ` 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=20200713082203.GA793133@kheib-workstation \
    --to=kamalheib1@gmail.com \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.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).