From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bernard Metzler <bmt@zurich.ibm.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/1] Make user mmapped CQ arming flags field 32 bit size to remove 64 bit architecture dependency of siw.
Date: Tue, 6 Aug 2019 09:10:06 -0300 [thread overview]
Message-ID: <20190806121006.GC11627@ziepe.ca> (raw)
In-Reply-To: <20190805141708.9004-2-bmt@zurich.ibm.com>
On Mon, Aug 05, 2019 at 04:17:08PM +0200, Bernard Metzler wrote:
> Signed-off-by: Bernard Metzler <bmt@zurich.ibm.com>
> ---
Don't send patches with empty commit messages. Every patch must have a
comprehensive commit message from now on.
> drivers/infiniband/sw/siw/Kconfig | 2 +-
> drivers/infiniband/sw/siw/siw.h | 2 +-
> drivers/infiniband/sw/siw/siw_qp.c | 14 ++++++++++----
> drivers/infiniband/sw/siw/siw_verbs.c | 16 +++++++++++-----
> include/uapi/rdma/siw-abi.h | 3 ++-
> 5 files changed, 25 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/infiniband/sw/siw/Kconfig b/drivers/infiniband/sw/siw/Kconfig
> index dace276aea14..b622fc62f2cd 100644
> --- a/drivers/infiniband/sw/siw/Kconfig
> +++ b/drivers/infiniband/sw/siw/Kconfig
> @@ -1,6 +1,6 @@
> config RDMA_SIW
> tristate "Software RDMA over TCP/IP (iWARP) driver"
> - depends on INET && INFINIBAND && LIBCRC32C && 64BIT
> + depends on INET && INFINIBAND && LIBCRC32C
> select DMA_VIRT_OPS
> help
> This driver implements the iWARP RDMA transport over
> diff --git a/drivers/infiniband/sw/siw/siw.h b/drivers/infiniband/sw/siw/siw.h
> index 03fd7b2f595f..77b1aabf6ff3 100644
> --- a/drivers/infiniband/sw/siw/siw.h
> +++ b/drivers/infiniband/sw/siw/siw.h
> @@ -214,7 +214,7 @@ struct siw_wqe {
> struct siw_cq {
> struct ib_cq base_cq;
> spinlock_t lock;
> - u64 *notify;
> + struct siw_cq_ctrl *notify;
> struct siw_cqe *queue;
> u32 cq_put;
> u32 cq_get;
> diff --git a/drivers/infiniband/sw/siw/siw_qp.c b/drivers/infiniband/sw/siw/siw_qp.c
> index e27bd5b35b96..0990307c5d2c 100644
> --- a/drivers/infiniband/sw/siw/siw_qp.c
> +++ b/drivers/infiniband/sw/siw/siw_qp.c
> @@ -1013,18 +1013,24 @@ int siw_activate_tx(struct siw_qp *qp)
> */
> static bool siw_cq_notify_now(struct siw_cq *cq, u32 flags)
> {
> - u64 cq_notify;
> + u32 cq_notify;
>
> if (!cq->base_cq.comp_handler)
> return false;
>
> - cq_notify = READ_ONCE(*cq->notify);
> + /* Read application shared notification state */
> + cq_notify = READ_ONCE(cq->notify->flags);
>
> if ((cq_notify & SIW_NOTIFY_NEXT_COMPLETION) ||
> ((cq_notify & SIW_NOTIFY_SOLICITED) &&
> (flags & SIW_WQE_SOLICITED))) {
> - /* dis-arm CQ */
> - smp_store_mb(*cq->notify, SIW_NOTIFY_NOT);
> + /*
> + * CQ notification is one-shot: Since the
> + * current CQE causes user notification,
> + * the CQ gets dis-aremd and must be re-aremd
> + * by the user for a new notification.
> + */
> + WRITE_ONCE(cq->notify->flags, SIW_NOTIFY_NOT);
>
> return true;
> }
> diff --git a/drivers/infiniband/sw/siw/siw_verbs.c b/drivers/infiniband/sw/siw/siw_verbs.c
> index 32dc79d0e898..e7f3a2379d9d 100644
> --- a/drivers/infiniband/sw/siw/siw_verbs.c
> +++ b/drivers/infiniband/sw/siw/siw_verbs.c
> @@ -1049,7 +1049,7 @@ int siw_create_cq(struct ib_cq *base_cq, const struct ib_cq_init_attr *attr,
>
> spin_lock_init(&cq->lock);
>
> - cq->notify = &((struct siw_cq_ctrl *)&cq->queue[size])->notify;
> + cq->notify = (struct siw_cq_ctrl *)&cq->queue[size];
>
> if (udata) {
> struct siw_uresp_create_cq uresp = {};
> @@ -1141,11 +1141,17 @@ int siw_req_notify_cq(struct ib_cq *base_cq, enum ib_cq_notify_flags flags)
> siw_dbg_cq(cq, "flags: 0x%02x\n", flags);
>
> if ((flags & IB_CQ_SOLICITED_MASK) == IB_CQ_SOLICITED)
> - /* CQ event for next solicited completion */
> - smp_store_mb(*cq->notify, SIW_NOTIFY_SOLICITED);
> + /*
> + * Enable CQ event for next solicited completion.
> + * and make it visible to all associated producers.
> + */
> + smp_store_mb(cq->notify->flags, SIW_NOTIFY_SOLICITED);
> else
> - /* CQ event for any signalled completion */
> - smp_store_mb(*cq->notify, SIW_NOTIFY_ALL);
> + /*
> + * Enable CQ event for any signalled completion.
> + * and make it visible to all associated producers.
> + */
> + smp_store_mb(cq->notify->flags, SIW_NOTIFY_ALL);
this isn't what we talked about, is it?
> index 7de68f1dc707..af735f55b291 100644
> --- a/include/uapi/rdma/siw-abi.h
> +++ b/include/uapi/rdma/siw-abi.h
> @@ -180,6 +180,7 @@ struct siw_cqe {
> * to control CQ arming.
> */
> struct siw_cq_ctrl {
> - __aligned_u64 notify;
> + __u32 flags;
> + __u32 pad;
The commit message needs to explain why this is compatible with
existing user space, if it is even is safe..
Jason
next prev parent reply other threads:[~2019-08-06 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:17 [PATCH 0/1] Fix siw CQ processing for 32 bit archtecture support Bernard Metzler
2019-08-05 14:17 ` [PATCH 1/1] Make user mmapped CQ arming flags field 32 bit size to remove 64 bit architecture dependency of siw Bernard Metzler
2019-08-05 17:09 ` Leon Romanovsky
2019-08-06 11:58 ` Bernard Metzler
2019-08-06 12:10 ` Jason Gunthorpe [this message]
2019-08-06 12:32 ` Doug Ledford
2019-08-06 13:09 ` Bernard Metzler
2019-08-06 14:53 ` Bernard Metzler
2019-08-06 15:31 ` Jason Gunthorpe
2019-08-06 16:36 ` Bernard Metzler
2019-08-06 16:39 ` Jason Gunthorpe
2019-08-06 17:01 ` Bernard Metzler
2019-08-06 17:35 ` Jason Gunthorpe
2019-08-07 17:49 ` Bernard Metzler
2019-08-07 18:53 ` Doug Ledford
2019-08-08 14:17 ` Bernard Metzler
2019-08-08 15:39 ` Jason Gunthorpe
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=20190806121006.GC11627@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bmt@zurich.ibm.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