Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Kamal Heib <kamalheib1@gmail.com>
To: linux-rdma@vger.kernel.org
Cc: Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Michal Kalderon <mkalderon@marvell.com>,
	Potnuri Bharat Teja <bharat@chelsio.com>,
	Shiraz Saleem <shiraz.saleem@intel.com>,
	Bernard Metzler <bmt@zurich.ibm.com>
Subject: Re: [PATCH for-next 0/7] RDMA: Remove query_pkey from iwarp providers
Date: Tue, 14 Jul 2020 21:26:27 +0300	[thread overview]
Message-ID: <20200714182627.GA58593@kheib-workstation> (raw)
In-Reply-To: <20200714081038.13131-1-kamalheib1@gmail.com>

On Tue, Jul 14, 2020 at 11:10:31AM +0300, Kamal Heib wrote:
> This patch set does the following:
> 1- Avoid exposing the pkeys sysfs entries for iwarp providers.
> 2- Avoid allocating the pkey cache for iwarp providers.
> 3- Remove the requirement by RDMA core to implement query_pkey
>    by all providers.
> 4- Remove the implementation of query_pkey callback from iwarp providers.
> 
> Kamal Heib (7):
>   RDMA/core: Expose pkeys sysfs files only if pkey_tbl_len is set
>   RDMA/core: Allocate the pkey cache only if the pkey_tbl_len is set
>   RDMA/core: Remove query_pkey from the mandatory ops
>   RDMA/siw: Remove the query_pkey callback
>   RDMA/cxgb4: Remove the query_pkey callback
>   RDMA/i40iw: Remove the query_pkey callback
>   RDMA/qedr: Remove the query_pkey callback
> 
>  drivers/infiniband/core/cache.c           | 45 ++++++++++------
>  drivers/infiniband/core/device.c          |  4 +-
>  drivers/infiniband/core/sysfs.c           | 64 ++++++++++++++++-------
>  drivers/infiniband/hw/cxgb4/provider.c    | 11 ----
>  drivers/infiniband/hw/i40iw/i40iw_verbs.c | 19 -------
>  drivers/infiniband/hw/qedr/main.c         |  3 +-
>  drivers/infiniband/hw/qedr/verbs.c        |  1 -
>  drivers/infiniband/sw/siw/siw_main.c      |  1 -
>  drivers/infiniband/sw/siw/siw_verbs.c     |  9 ----
>  drivers/infiniband/sw/siw/siw_verbs.h     |  1 -
>  10 files changed, 77 insertions(+), 81 deletions(-)
> 
> -- 
> 2.25.4
> 

I found an issue while testing this patch set, I'll post a v1 that
fixes this issue soon.

Nacked-by: Kamal Heib <kamalheib1@gmail.com>

      parent reply	other threads:[~2020-07-14 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  8:10 [PATCH for-next 0/7] RDMA: Remove query_pkey from iwarp providers Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 1/7] RDMA/core: Expose pkeys sysfs files only if pkey_tbl_len is set Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 2/7] RDMA/core: Allocate the pkey cache only if the " Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 3/7] RDMA/core: Remove query_pkey from the mandatory ops Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 4/7] RDMA/siw: Remove the query_pkey callback Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 5/7] RDMA/cxgb4: " Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 6/7] RDMA/i40iw: " Kamal Heib
2020-07-14  8:10 ` [PATCH for-next 7/7] RDMA/qedr: " Kamal Heib
2020-07-14  9:14   ` Michal Kalderon
2020-07-14 18:26 ` 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=20200714182627.GA58593@kheib-workstation \
    --to=kamalheib1@gmail.com \
    --cc=bharat@chelsio.com \
    --cc=bmt@zurich.ibm.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mkalderon@marvell.com \
    --cc=shiraz.saleem@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox