From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Aharon Landau <aharonl@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Michael Guralnik <michaelgur@nvidia.com>
Subject: Re: [PATCH rdma-next 00/12] Refactor UMR post send logic
Date: Mon, 25 Apr 2022 15:48:24 -0300 [thread overview]
Message-ID: <20220425184824.GA2247544@nvidia.com> (raw)
In-Reply-To: <cover.1649747695.git.leonro@nvidia.com>
On Tue, Apr 12, 2022 at 10:23:55AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> UMR are special QPs that require slightly different logic than other
> QPs. This series from Aharon refactors the logic around UMR QP to
> separate file and functions to clean the post send flow.
>
> Thanks
>
> Aharon Landau (12):
> RDMA/mlx5: Move init and cleanup of UMR to umr.c
> RDMA/mlx5: Move umr checks to umr.h
> RDMA/mlx5: Move mkey ctrl segment logic to umr.c
> RDMA/mlx5: Simplify get_umr_update_access_mask()
> RDMA/mlx5: Expose wqe posting helpers outside of wr.c
> RDMA/mlx5: Introduce mlx5_umr_post_send_wait()
> RDMA/mlx5: Use mlx5_umr_post_send_wait() to revoke MRs
> RDMA/mlx5: Use mlx5_umr_post_send_wait() to rereg pd access
> RDMA/mlx5: Move creation and free of translation tables to umr.c
> RDMA/mlx5: Use mlx5_umr_post_send_wait() to update MR pas
> RDMA/mlx5: Use mlx5_umr_post_send_wait() to update xlt
> RDMA/mlx5: Clean UMR QP type flow from mlx5_ib_post_send()
I moved the static to the earlier patch, but otherwise applied to
for-next, thanks
Jason
prev parent reply other threads:[~2022-04-25 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 7:23 [PATCH rdma-next 00/12] Refactor UMR post send logic Leon Romanovsky
2022-04-12 7:23 ` [PATCH rdma-next 01/12] RDMA/mlx5: Move init and cleanup of UMR to umr.c Leon Romanovsky
2022-04-12 7:23 ` [PATCH rdma-next 02/12] RDMA/mlx5: Move umr checks to umr.h Leon Romanovsky
2022-04-12 7:23 ` [PATCH rdma-next 03/12] RDMA/mlx5: Move mkey ctrl segment logic to umr.c Leon Romanovsky
2022-04-25 15:22 ` Jason Gunthorpe
2022-04-12 7:23 ` [PATCH rdma-next 04/12] RDMA/mlx5: Simplify get_umr_update_access_mask() Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 05/12] RDMA/mlx5: Expose wqe posting helpers outside of wr.c Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 06/12] RDMA/mlx5: Introduce mlx5_umr_post_send_wait() Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 07/12] RDMA/mlx5: Use mlx5_umr_post_send_wait() to revoke MRs Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 08/12] RDMA/mlx5: Use mlx5_umr_post_send_wait() to rereg pd access Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 09/12] RDMA/mlx5: Move creation and free of translation tables to umr.c Leon Romanovsky
2022-04-25 15:11 ` Jason Gunthorpe
2022-04-12 7:24 ` [PATCH rdma-next 10/12] RDMA/mlx5: Use mlx5_umr_post_send_wait() to update MR pas Leon Romanovsky
2022-04-25 17:43 ` Jason Gunthorpe
2022-04-12 7:24 ` [PATCH rdma-next 11/12] RDMA/mlx5: Use mlx5_umr_post_send_wait() to update xlt Leon Romanovsky
2022-04-12 7:24 ` [PATCH rdma-next 12/12] RDMA/mlx5: Clean UMR QP type flow from mlx5_ib_post_send() Leon Romanovsky
2022-04-25 18:48 ` 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=20220425184824.GA2247544@nvidia.com \
--to=jgg@nvidia.com \
--cc=aharonl@nvidia.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@nvidia.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).