From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH rdma-next v1 0/2] Align write() and ioctl() paths
Date: Thu, 16 Jul 2020 13:39:54 +0300 [thread overview]
Message-ID: <20200716103956.1422139-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Changelog:
v1:
* v0 revealed old bug https://lore.kernel.org/linux-rdma/20200716102059.1420681-1-leon@kernel.org
that took a while to find.
* create_cq() was rewritten to make sure that uobj is properly initialized.
v0: https://lore.kernel.org/lkml/20200708110554.1270613-1-leon@kernel.org
----------------------------------------------------
Hi,
The discussion about RWQ table patch revealed incosistency with use of
usecnt, complex unwind flows without any reason and difference between
write() and ioctl() paths.
This series extends infrastructure to be consistent, reliable and
predicable in regards of commit/desotry uobject.
Thanks
Leon Romanovsky (2):
RDMA/core: Align abort/commit object scheme for write() and ioctl()
paths
RDMA/core: Update write interface to use automatic object lifetime
drivers/infiniband/core/uverbs_cmd.c | 314 ++++++------------
drivers/infiniband/core/uverbs_main.c | 4 +
.../infiniband/core/uverbs_std_types_device.c | 7 +-
include/rdma/uverbs_ioctl.h | 1 +
include/rdma/uverbs_std_types.h | 14 +
5 files changed, 120 insertions(+), 220 deletions(-)
--
2.26.2
reply other threads:[~2020-07-16 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200716103956.1422139-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.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).