From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: [PATCH rdma-next 0/3] Add support for dynamic UAR usage
Date: Sun, 24 Dec 2017 16:31:33 +0200 [thread overview]
Message-ID: <20171224143136.12306-1-leon@kernel.org> (raw)
>From Yishai:
This series enables the user space driver to ask for a dynamic UAR
allocation and uses its internal BF (i.e. blue-flame) registers as part
of QP creation.
The motivation behind this functionality is to let the user space driver
share BF register between few QPs or to set a dedicated BF for a given QP.
The above gives an option to user space applications to utilize its
resources and performance according to its needs.
For example:
An application can improve its performance by having a dedicated BF for
collection of QPs that are running from the same thread and drop the
need to take a lock as part of its post send flow. This is not enabled
today as the kernel driver assigned BF registers in some FIFO logic and
as such QPs from different threads may share same BF and as such a lock
when accessing this BF will be needed.
The series consists from 3 patches:
The first patch extends the alloc context flow to be prepared for
working with dynamic UAR allocations.
The second patch exposes the option to dynamic allocates a UAR.
The third patch uses the given BF register from the user area as
part of QP creation instead of using some arbitrary BF register.
The patches are available in the git repository at:
git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git tags/rdma-next-2017-12-24-5
Thanks
---------------------------------------
Yishai Hadas (3):
IB/mlx5: Extend UAR stuff to support dynamic allocation
IB/mlx5: Expose dynamic mmap allocation
IB/mlx5: Enable QP creation with a given blue flame index
drivers/infiniband/hw/mlx5/main.c | 141 ++++++++++++++++++++++++++++-------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 13 +++-
drivers/infiniband/hw/mlx5/qp.c | 55 ++++++++++----
include/linux/mlx5/device.h | 2 +
include/linux/mlx5/driver.h | 3 +
include/uapi/rdma/mlx5-abi.h | 5 +-
6 files changed, 177 insertions(+), 42 deletions(-)
--
2.15.1
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-12-24 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 14:31 Leon Romanovsky [this message]
[not found] ` <20171224143136.12306-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-12-24 14:31 ` [PATCH rdma-next 1/3] IB/mlx5: Extend UAR stuff to support dynamic allocation Leon Romanovsky
2017-12-24 14:31 ` [PATCH rdma-next 2/3] IB/mlx5: Expose dynamic mmap allocation Leon Romanovsky
2017-12-24 14:31 ` [PATCH rdma-next 3/3] IB/mlx5: Enable QP creation with a given blue flame index Leon Romanovsky
2017-12-28 20:01 ` [PATCH rdma-next 0/3] Add support for dynamic UAR usage 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=20171224143136.12306-1-leon@kernel.org \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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