From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>, linux-rdma@vger.kernel.org
Cc: Jiri Pirko <jiri@resnulli.us>,
patches@lists.linux.dev,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: [PATCH 0/6] Remove driver dependencies on ib_uverbs.ko
Date: Wed, 13 May 2026 14:33:22 -0300 [thread overview]
Message-ID: <0-v1-045258567bd6+9fe-ib_uverbs_support_ko_jgg@nvidia.com> (raw)
The original design was for user facing modules like ib_uverbs to be
independently loadable, if the user didn't want to have those char devs
then they could block the module.
This has slowly gotten degraded over time and right now every driver is
depending on ib_uverbs.ko. Fixup everything except
rdma_user_mmap_disassociate() in hns by moving coding around and adding a
new module ib_uverbs_support.ko to hold the dirver functions without any
of the uverbs cdev code.
After this series mlx5_ib and bnxt_re will use ib_uverbs_support.ko.
The first patch should go to rc
Jason Gunthorpe (6):
RDMA/core: Move the _ib_copy_validate_udata* functions to
ib_core_uverbs
RDMA/core: Move many of the little EXPORTs from uverbs_ioctl into
ib_core_uverbs
RDMA/core: Remove uverbs_async_event_release()
RDMA/core: Make a new module for the uverbs components needed by
drivers
RDMA/core: Move ucaps into ib_uverbs_support.ko
RDMA/core: Move flow related functions to ib_uverbs_support.ko
drivers/infiniband/core/Makefile | 13 +-
drivers/infiniband/core/ib_core_uverbs.c | 305 ++++++++++++++++
drivers/infiniband/core/rdma_core.c | 150 ++++----
drivers/infiniband/core/rdma_core.h | 1 -
drivers/infiniband/core/ucaps.c | 6 +-
drivers/infiniband/core/uverbs.h | 60 +++-
drivers/infiniband/core/uverbs_cmd.c | 76 ----
drivers/infiniband/core/uverbs_flow.c | 78 +++++
drivers/infiniband/core/uverbs_ioctl.c | 326 ------------------
drivers/infiniband/core/uverbs_main.c | 127 +++----
drivers/infiniband/core/uverbs_std_types.c | 6 -
.../core/uverbs_std_types_async_fd.c | 22 +-
drivers/infiniband/core/uverbs_uapi.c | 13 +
include/rdma/ib_ucaps.h | 1 -
include/rdma/uverbs_types.h | 8 +-
15 files changed, 628 insertions(+), 564 deletions(-)
create mode 100644 drivers/infiniband/core/uverbs_flow.c
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
--
2.43.0
next reply other threads:[~2026-05-13 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 17:33 Jason Gunthorpe [this message]
2026-05-13 17:33 ` [PATCH 1/6] RDMA/core: Move the _ib_copy_validate_udata* functions to ib_core_uverbs Jason Gunthorpe
2026-05-15 23:12 ` Jason Gunthorpe
2026-05-13 17:33 ` [PATCH 2/6] RDMA/core: Move many of the little EXPORTs from uverbs_ioctl into ib_core_uverbs Jason Gunthorpe
2026-05-13 17:33 ` [PATCH 3/6] RDMA/core: Remove uverbs_async_event_release() Jason Gunthorpe
2026-05-13 17:33 ` [PATCH 4/6] RDMA/core: Make a new module for the uverbs components needed by drivers Jason Gunthorpe
2026-05-13 17:33 ` [PATCH 5/6] RDMA/core: Move ucaps into ib_uverbs_support.ko Jason Gunthorpe
2026-05-13 17:33 ` [PATCH 6/6] RDMA/core: Move flow related functions to ib_uverbs_support.ko Jason Gunthorpe
2026-05-15 18:23 ` kernel test robot
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=0-v1-045258567bd6+9fe-ib_uverbs_support_ko_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=sriharsha.basavapatna@broadcom.com \
/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