From: Jason Gunthorpe <jgg@ziepe.ca>
To: Konstantin Taranov <kotaranov@microsoft.com>
Cc: Long Li <longli@microsoft.com>,
Konstantin Taranov <kotaranov@linux.microsoft.com>,
Shiraz Saleem <shirazsaleem@microsoft.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH rdma-next v3 1/1] RDMA/mana_ib: UC QP support for UAPI
Date: Tue, 9 Jun 2026 09:39:31 -0300 [thread overview]
Message-ID: <20260609123931.GH2764304@ziepe.ca> (raw)
In-Reply-To: <PAWPR83MB098460109147A819963260A9B41D2@PAWPR83MB0984.EURPRD83.prod.outlook.com>
On Tue, Jun 09, 2026 at 09:40:30AM +0000, Konstantin Taranov wrote:
> > > +int mana_ib_gd_destroy_rnic_qp(struct mana_ib_dev *mdev, struct
> > > +mana_ib_qp *qp)
> >
> > The function is renamed to _rnic_ to be shared between RC and UC, but the
> > request/response structs are still named _rc_. Should these be renamed to
> > _rnic_ as well for consistency? Or does the firmware use the same destroy
> > command for both QP types?
>
> Sure, they can be renamed. In the firmware, it is still called RC though, but it can
> be used for all QP types (even UD). So, the name _rc_ is just historical.
>
> Long, do you want me to rename it?
>
> Jason, can the patch series accepted, or do I need to send
> IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA first?
Yeah, that's what I want to start seeing
And use the proper helpers too:
+ err = ib_copy_to_udata(udata, &resp, min(sizeof(resp), udata->outlen));
+ if (err)
+ goto destroy_qp;
Thats ib_respond_udata() now too
Jason
next prev parent reply other threads:[~2026-06-09 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 10:06 [PATCH rdma-next v3 1/1] RDMA/mana_ib: UC QP support for UAPI Konstantin Taranov
2026-06-05 1:32 ` Long Li
2026-06-09 9:40 ` Konstantin Taranov
2026-06-09 12:39 ` Jason Gunthorpe [this message]
2026-06-09 19:19 ` Long Li
-- strict thread matches above, loose matches on Subject: below --
2026-04-16 14:02 Konstantin Taranov
2026-04-16 19:52 ` Long Li
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=20260609123931.GH2764304@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=kotaranov@linux.microsoft.com \
--cc=kotaranov@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=shirazsaleem@microsoft.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