From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eli Cohen <eli@mellanox.com>,
Haggai Abramonvsky <hagaya@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
"majd@mellanox.com" <majd@mellanox.com>,
Matan Barak <matanb@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Roland Dreier <roland@purestorage.com>,
Sagi Grimberg <sagi@grimberg.me>,
Yishai Hadas <yishaih@mellanox.com>
Subject: [PATCH rdma-next 0/6] Use ib_umem_find_best_pgsz() for all umems
Date: Mon, 26 Oct 2020 15:26:29 +0200 [thread overview]
Message-ID: <20201026132635.1337663-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
From Jason:
Move the remaining cases working with umems to use versions of
ib_umem_find_best_pgsz() tailored to the calculations the devices
requires.
Unlike a MR there is no IOVA, instead a page offset from the starting page
is possible, with various restrictions.
Compute the best page size to meet the page_offset restrictions.
Thanks
Jason Gunthorpe (6):
RDMA/mlx5: Use ib_umem_find_best_pgsz() for devx
RDMA/mlx5: Use ib_umem_find_best_pgoff() for SRQ
RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for WQ
RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for QP
RDMA/mlx5: mlx5_umem_find_best_quantized_pgoff() for CQ
RDMA/mlx5: Lower setting the umem's PAS for SRQ
drivers/infiniband/hw/mlx5/cq.c | 48 ++++++++---
drivers/infiniband/hw/mlx5/devx.c | 56 ++++++------
drivers/infiniband/hw/mlx5/mem.c | 115 +++++++++----------------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 56 ++++++++++--
drivers/infiniband/hw/mlx5/qp.c | 124 ++++++++++++---------------
drivers/infiniband/hw/mlx5/srq.c | 27 +-----
drivers/infiniband/hw/mlx5/srq.h | 1 +
drivers/infiniband/hw/mlx5/srq_cmd.c | 80 ++++++++++++++++-
include/rdma/ib_umem.h | 42 +++++++++
9 files changed, 326 insertions(+), 223 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-26 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 13:26 Leon Romanovsky [this message]
2020-10-26 13:26 ` [PATCH rdma-next 1/6] RDMA/mlx5: Use ib_umem_find_best_pgsz() for devx Leon Romanovsky
2020-10-26 13:26 ` [PATCH rdma-next 2/6] RDMA/mlx5: Use ib_umem_find_best_pgoff() for SRQ Leon Romanovsky
2020-10-26 13:26 ` [PATCH rdma-next 3/6] RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for WQ Leon Romanovsky
2020-10-26 14:42 ` Gal Pressman
2020-10-27 6:03 ` Leon Romanovsky
2020-10-26 13:26 ` [PATCH rdma-next 4/6] RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for QP Leon Romanovsky
2020-10-26 13:26 ` [PATCH rdma-next 5/6] RDMA/mlx5: mlx5_umem_find_best_quantized_pgoff() for CQ Leon Romanovsky
2020-10-26 13:26 ` [PATCH rdma-next 6/6] RDMA/mlx5: Lower setting the umem's PAS for SRQ Leon Romanovsky
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=20201026132635.1337663-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=hagaya@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=majd@mellanox.com \
--cc=matanb@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roland@purestorage.com \
--cc=sagi@grimberg.me \
--cc=yishaih@mellanox.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;
as well as URLs for NNTP newsgroup(s).