From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Doug Ledford <dledford@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma/siw: avoid smp_store_mb() on a u64
Date: Fri, 12 Jul 2019 09:03:28 -0300 [thread overview]
Message-ID: <20190712120328.GB27512@ziepe.ca> (raw)
In-Reply-To: <OF05C1A780.433E36D1-ON00258435.003381DA-00258435.003F847E@notes.na.collabserv.com>
On Fri, Jul 12, 2019 at 11:33:46AM +0000, Bernard Metzler wrote:
> >diff --git a/drivers/infiniband/sw/siw/siw_verbs.c
> >b/drivers/infiniband/sw/siw/siw_verbs.c
> >index 32dc79d0e898..41c5ab293fe1 100644
> >+++ b/drivers/infiniband/sw/siw/siw_verbs.c
> >@@ -1142,10 +1142,11 @@ int siw_req_notify_cq(struct ib_cq *base_cq,
> >enum ib_cq_notify_flags flags)
> >
> > if ((flags & IB_CQ_SOLICITED_MASK) == IB_CQ_SOLICITED)
> > /* CQ event for next solicited completion */
> >- smp_store_mb(*cq->notify, SIW_NOTIFY_SOLICITED);
> >+ WRITE_ONCE(*cq->notify, SIW_NOTIFY_SOLICITED);
> > else
> > /* CQ event for any signalled completion */
> >- smp_store_mb(*cq->notify, SIW_NOTIFY_ALL);
> >+ WRITE_ONCE(*cq->notify, SIW_NOTIFY_ALL);
> >+ smp_wmb();
> >
> > if (flags & IB_CQ_REPORT_MISSED_EVENTS)
> > return cq->cq_put - cq->cq_get;
>
>
> Hi Arnd,
> Many thanks for pointing that out! Indeed, this CQ notification
> mechanism does not take 32 bit architectures into account.
> Since we have only three flags to hold here, it's probably better
> to make it a 32bit value. That would remove the issue w/o
> introducing extra smp_wmb().
I also prefer not to see smp_wmb() in drivers..
> I'd prefer smp_store_mb(), since on some architectures it shall be
> more efficient. That would also make it sufficient to use
> READ_ONCE.
The READ_ONCE is confusing to me too, if you need store_release
semantics then the reader also needs to pair with load_acquite -
otherwise it doesn't work.
Still, we need to do something rapidly to fix the i386 build, please
revise right away..
Jason
next prev parent reply other threads:[~2019-07-12 12:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 8:51 [PATCH] rdma/siw: avoid smp_store_mb() on a u64 Arnd Bergmann
2019-07-12 11:33 ` Bernard Metzler
2019-07-12 11:47 ` Peter Zijlstra
2019-07-12 12:03 ` Jason Gunthorpe [this message]
2019-07-12 12:27 ` Bernard Metzler
2019-07-12 13:05 ` Bernard Metzler
2019-07-12 13:19 ` Peter Zijlstra
2019-07-12 13:35 ` Bernard Metzler
2019-07-12 13:22 ` Arnd Bergmann
2019-07-12 15:14 ` Jason Gunthorpe
2019-07-12 20:24 ` Arnd Bergmann
2019-07-12 13:53 ` Jason Gunthorpe
2019-07-12 14:35 ` Bernard Metzler
2019-07-12 14:42 ` Jason Gunthorpe
2019-07-12 15:24 ` Bernard Metzler
2019-07-12 15:32 ` Jason Gunthorpe
2019-07-12 17:40 ` Bernard Metzler
2019-07-12 17:45 ` Jason Gunthorpe
2019-07-12 18:06 ` Bernard Metzler
2019-07-12 16:12 ` Peter Zijlstra
2019-07-25 17:23 ` 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=20190712120328.GB27512@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=BMT@zurich.ibm.com \
--cc=arnd@arndb.de \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=peterz@infradead.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