From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Jianbo Liu <jianbol@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH rdma-next 2/3] IB/mlx5: Create UMR QP just before first reg_mr occurs
Date: Thu, 13 Jun 2024 21:06:00 +0300 [thread overview]
Message-ID: <20240613180600.GG4966@unreal> (raw)
In-Reply-To: <20240607173003.GN19897@nvidia.com>
On Fri, Jun 07, 2024 at 02:30:03PM -0300, Jason Gunthorpe wrote:
> On Mon, Jun 03, 2024 at 01:26:38PM +0300, Leon Romanovsky wrote:
> > From: Jianbo Liu <jianbol@nvidia.com>
> >
> > UMR QP is not used in some cases, so move QP and its CQ creations from
> > driver load flow to the time first reg_mr occurs, that is when MR
> > interfaces are first called.
>
> We use UMR for kernel MRs too, don't we?
Strange, I know that I answered to this email, but I don't see it in the ML.
As far as I checked, we are not. Did I miss something?
Thanks
>
> Jason
next prev parent reply other threads:[~2024-06-13 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 10:26 [PATCH rdma-next 0/3] Delay mlx5_ib internal resources allocations Leon Romanovsky
2024-06-03 10:26 ` [PATCH mlx5-next 1/3] net/mlx5: Reimplement write combining test Leon Romanovsky
2024-06-03 10:26 ` [PATCH rdma-next 2/3] IB/mlx5: Create UMR QP just before first reg_mr occurs Leon Romanovsky
2024-06-07 17:30 ` Jason Gunthorpe
2024-06-13 18:06 ` Leon Romanovsky [this message]
2024-06-13 19:12 ` Zhu Yanjun
2024-06-13 19:24 ` Leon Romanovsky
2024-06-17 14:24 ` Jason Gunthorpe
2024-06-03 10:26 ` [PATCH rdma-next 3/3] IB/mlx5: Allocate resources just before first QP/SRQ is created Leon Romanovsky
2024-06-16 15:38 ` (subset) [PATCH rdma-next 0/3] Delay mlx5_ib internal resources allocations 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=20240613180600.GG4966@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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).