From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Artemy Kovalyov <artemyko@mellanox.com>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
Moni Shoua <monis@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>
Subject: Re: [PATCH rdma-next 0/5] Reorganize mlx5 UMR creation flow
Date: Fri, 18 Sep 2020 13:05:32 -0300 [thread overview]
Message-ID: <20200918160532.GA320440@nvidia.com> (raw)
In-Reply-To: <20200914112653.345244-1-leon@kernel.org>
On Mon, Sep 14, 2020 at 02:26:48PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> This flow has become crufty and confusing. Revise it so that the rules
> on how UMR is used with MRs is much clearer and more correct.
>
> Fixes a few minor bugs in ODP and rereg_mr where disallowed things were
> not properly blocked.
>
> Thanks
>
> Jason Gunthorpe (5):
> RDMA/mlx5: Remove dead check for EAGAIN after alloc_mr_from_cache()
> RDMA/mlx5: Use set_mkc_access_pd_addr_fields() in reg_create()
> RDMA/mlx5: Make mkeys always owned by the kernel's PD when not enabled
> RDMA/mlx5: Disable IB_DEVICE_MEM_MGT_EXTENSIONS if IB_WR_REG_MR can't
> work
> RDMA/mlx5: Clarify what the UMR is for when creating MRs
Applied to for-next
Jason
prev parent reply other threads:[~2020-09-18 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 11:26 Leon Romanovsky
2020-09-18 16:05 ` 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=20200918160532.GA320440@nvidia.com \
--to=jgg@nvidia.com \
--cc=artemyko@mellanox.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--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
Powered by JetHome