From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Patrisious Haddad <phaddad@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH mlx5-next 1/2] net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain
Date: Thu, 26 Jun 2025 09:49:43 +0300 [thread overview]
Message-ID: <20250626064943.GG17401@unreal> (raw)
In-Reply-To: <20250625164200.45fb717d@kernel.org>
On Wed, Jun 25, 2025 at 04:42:00PM -0700, Jakub Kicinski wrote:
> On Tue, 17 Jun 2025 11:19:15 +0300 Leon Romanovsky wrote:
> > + for (i = 0; i < MLX5_RDMA_TRANSPORT_BYPASS_PRIO; i++) {
> > + prio = fs_create_prio(&root_ns->ns, i, 1);
> > + if (IS_ERR(prio))
> > + return PTR_ERR(prio);
> > + }
> > + set_prio_attrs(root_ns);
>
> Looking at the PR now -- y'all sure this doesn't need any extra cleanup
> if creation of non-first prio fails?
Yes, it was missed.
Thanks
next prev parent reply other threads:[~2025-06-26 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 8:19 [PATCH rdma-next 0/2] Add multiple priorities support to mlx5 RDMA TRANSPORT tables Leon Romanovsky
2025-06-17 8:19 ` [PATCH mlx5-next 1/2] net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain Leon Romanovsky
2025-06-25 23:42 ` Jakub Kicinski
2025-06-26 6:49 ` Leon Romanovsky [this message]
2025-06-17 8:19 ` [PATCH rdma-next 2/2] RDMA/mlx5: Add multiple priorities support to RDMA TRANSPORT userspace tables Leon Romanovsky
2025-06-18 4:53 ` [PATCH rdma-next 0/2] Add multiple priorities support to mlx5 RDMA TRANSPORT tables Zhu Yanjun
2025-06-18 10:39 ` 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=20250626064943.GG17401@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.