From: Bernard Metzler <bmt@zurich.ibm.com>
To: linux-rdma@vger.kernel.org
Cc: jgg@ziepe.ca, Bernard Metzler <bmt@zurich.ibm.com>
Subject: [PATCH 0/1] Fix siw CQ processing for 32 bit archtecture support
Date: Mon, 5 Aug 2019 16:17:07 +0200 [thread overview]
Message-ID: <20190805141708.9004-1-bmt@zurich.ibm.com> (raw)
Change driver/user shared (mmapped) CQ notification flags field
to unaligned 32-bits size. This enables building siw on 32-bit
architectures.
The original idea to introduce test_and_clear_bit() for testing CQ
arming during CQE processing was abandoned, since it would
require architecture spcific siw-abi notation: test_and_clear_bit()
expects an unsigned long field, which has an architecture specific
size.
This patch applies to 5.3-rc3.
Bernard Metzler (1):
Make user mmapped CQ arming flags field 32 bit size to remove 64 bit
architecture dependency of siw.
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(-)
--
2.17.2
next reply other threads:[~2019-08-05 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:17 Bernard Metzler [this message]
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
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=20190805141708.9004-1-bmt@zurich.ibm.com \
--to=bmt@zurich.ibm.com \
--cc=jgg@ziepe.ca \
--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