linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bernard Metzler" <BMT@zurich.ibm.com>
To: "Jason Gunthorpe" <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org, krishna2@chelsio.com, leon@kernel.org
Subject: Re: Re: [PATCH for-next v2] RDMA/siw: Simplify QP representation.
Date: Sat, 4 Jan 2020 17:26:46 +0000	[thread overview]
Message-ID: <OF3A9B5234.ED8DBC50-ON002584E5.005FD59F-002584E5.005FD5A4@notes.na.collabserv.com> (raw)
In-Reply-To: <20200103195547.GA27379@ziepe.ca>


-----"Jason Gunthorpe" <jgg@ziepe.ca> wrote: -----

>To: "Bernard Metzler" <bmt@zurich.ibm.com>
>From: "Jason Gunthorpe" <jgg@ziepe.ca>
>Date: 01/03/2020 08:55PM
>Cc: linux-rdma@vger.kernel.org, krishna2@chelsio.com, leon@kernel.org
>Subject: [EXTERNAL] Re: [PATCH for-next v2] RDMA/siw: Simplify QP
>representation.
>
>On Tue, Dec 10, 2019 at 05:17:29PM +0100, Bernard Metzler wrote:
>> Change siw_qp to contain ib_qp. Use rdma_is_kernel_res()
>> on contained ib_qp to distinguish kernel level from user
>> level applications resources. Apply same mechanism for
>> kernel/user level application detection to completion queues.
>> 
>> Signed-off-by: Bernard Metzler <bmt@zurich.ibm.com>
>> ---
>> Changelog:
>> v1 -> v2: Use rdma_is_kernel_res() to detect
>>           kernel level application.
>> 
>>  drivers/infiniband/sw/siw/siw.h       | 26 +++---------
>>  drivers/infiniband/sw/siw/siw_cq.c    |  2 +-
>>  drivers/infiniband/sw/siw/siw_main.c  |  2 +-
>>  drivers/infiniband/sw/siw/siw_qp.c    | 13 +++---
>>  drivers/infiniband/sw/siw/siw_qp_rx.c |  6 +--
>>  drivers/infiniband/sw/siw/siw_qp_tx.c |  2 +-
>>  drivers/infiniband/sw/siw/siw_verbs.c | 61
>+++++++++++----------------
>>  7 files changed, 42 insertions(+), 70 deletions(-)
>> 
>> diff --git a/drivers/infiniband/sw/siw/siw.h
>b/drivers/infiniband/sw/siw/siw.h
>> index b939f489cd46..2bf7a7300343 100644
>> --- a/drivers/infiniband/sw/siw/siw.h
>> +++ b/drivers/infiniband/sw/siw/siw.h
>> @@ -7,6 +7,7 @@
>>  #define _SIW_H
>>  
>>  #include <rdma/ib_verbs.h>
>> +#include <rdma/restrack.h>
>>  #include <linux/socket.h>
>>  #include <linux/skbuff.h>
>>  #include <crypto/hash.h>
>> @@ -209,7 +210,6 @@ struct siw_cq {
>>  	u32 cq_put;
>>  	u32 cq_get;
>>  	u32 num_cqe;
>> -	bool kernel_verbs;
>>  	struct rdma_user_mmap_entry *cq_entry; /* mmap info for CQE array
>*/
>>  	u32 id; /* For debugging only */
>>  };
>> @@ -254,8 +254,8 @@ struct siw_srq {
>>  	u32 rq_get;
>>  	u32 num_rqe; /* max # of wqe's allowed */
>>  	struct rdma_user_mmap_entry *srq_entry; /* mmap info for SRQ
>array */
>> -	char armed; /* inform user if limit hit */
>> -	char kernel_verbs; /* '1' if kernel client */
>> +	bool armed; /* inform user if limit hit */
>> +	bool is_kernel_res; /* true if kernel client */
>>  };
>
>I changed these bools into bool bitfields, and applied to for-next
>
>Thanks,
>Jason
>
>
Hi Jason,
thanks a lot!


Bernard.


      parent reply	other threads:[~2020-01-04 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 16:17 [PATCH for-next v2] RDMA/siw: Simplify QP representation Bernard Metzler
2020-01-03 19:55 ` Jason Gunthorpe
2020-01-04 17:26 ` Bernard Metzler [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=OF3A9B5234.ED8DBC50-ON002584E5.005FD59F-002584E5.005FD5A4@notes.na.collabserv.com \
    --to=bmt@zurich.ibm.com \
    --cc=jgg@ziepe.ca \
    --cc=krishna2@chelsio.com \
    --cc=leon@kernel.org \
    --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).