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: Re: Re: Re: Re: [PATCH] rdma/siw: avoid smp_store_mb() on a u64
Date: Fri, 12 Jul 2019 14:45:25 -0300 [thread overview]
Message-ID: <20190712174525.GM27512@ziepe.ca> (raw)
In-Reply-To: <OFAB0712BA.E95178B5-ON00258435.00611CBE-00258435.00611CC4@notes.na.collabserv.com>
On Fri, Jul 12, 2019 at 05:40:43PM +0000, Bernard Metzler wrote:
> It is because there are two levels a CQ can be armed:
>
> #include <infiniband/verbs.h>
>
> int ibv_req_notify_cq(struct ibv_cq *cq, int solicited_only);
>
> If we kick the CQ handler, we have to clear the whole
> thing. The user later again decides how he wants to get it
> re-armed...SOLICITED completions only, or ALL signaled.
Arrange it so only one of the two bits is ever set and do two
test-and-set bits when a SOLICITED CQE comes in?
Jason
next prev parent reply other threads:[~2019-07-12 17:45 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
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 [this message]
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=20190712174525.GM27512@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