From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
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: Re: [PATCH rdma-next v1 0/7] Use ib_umem_find_best_pgsz() for all umems
Date: Mon, 16 Nov 2020 16:56:31 -0400 [thread overview]
Message-ID: <20201116205631.GA1626752@nvidia.com> (raw)
In-Reply-To: <20201115114311.136250-1-leon@kernel.org>
On Sun, Nov 15, 2020 at 01:43:04PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v1:
> * Added patch for raw QP
> * Fixed commit messages
> v0: https://lore.kernel.org/lkml/20201026132635.1337663-1-leon@kernel.org
>
> -------------------------
> >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 (7):
> RDMA/mlx5: Use ib_umem_find_best_pgoff() for SRQ
> RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for WQ
> RDMA/mlx5: Directly compute the PAS list for raw QP RQ's
> RDMA/mlx5: Use mlx5_umem_find_best_quantized_pgoff() for QP
> RDMA/mlx5: mlx5_umem_find_best_quantized_pgoff() for CQ
> RDMA/mlx5: Use ib_umem_find_best_pgsz() for devx
> RDMA/mlx5: Lower setting the umem's PAS for SRQ
Applied to for-next
Jason
prev parent reply other threads:[~2020-11-16 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 11:43 [PATCH rdma-next v1 0/7] Use ib_umem_find_best_pgsz() for all umems Leon Romanovsky
2020-11-16 20:56 ` Jason Gunthorpe [this message]
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=20201116205631.GA1626752@nvidia.com \
--to=jgg@nvidia.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=hagaya@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=leon@kernel.org \
--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