From: Jason Gunthorpe <jgg@ziepe.ca>
To: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH rdma-next v6 4/4] RDMA/bnxt_re: Direct Verbs: Support CQ and QP verbs
Date: Tue, 13 Jan 2026 13:28:13 -0400 [thread overview]
Message-ID: <20260113172813.GS745888@ziepe.ca> (raw)
In-Reply-To: <CAHHeUGWH6hujdXP6OheW-fFLLJ5WGjiJgcP41MYHC6sBZE+xbQ@mail.gmail.com>
On Tue, Jan 13, 2026 at 10:45:22PM +0530, Sriharsha Basavapatna wrote:
> > So why doesn't bnxt_qplib_destroy_cq() do the umem release and
> > req_put_nq?
> Because bnxt_qplib_destroy_cq() deals with only the FW side and the
> wrapper function bnxt_re_dv_create_qplib_cq() calls umem_get() and
> get_nq().
So make a wrapper function for destroy too..
Jason
next prev parent reply other threads:[~2026-01-13 17:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 4:25 [PATCH rdma-next v6 0/4] RDMA/bnxt_re: Support direct verbs Sriharsha Basavapatna
2025-12-24 4:25 ` [PATCH rdma-next v6 1/4] RDMA/bnxt_re: Move the UAPI methods to a dedicated file Sriharsha Basavapatna
2025-12-24 4:26 ` [PATCH rdma-next v6 2/4] RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function Sriharsha Basavapatna
2025-12-24 4:26 ` [PATCH rdma-next v6 3/4] RDMA/bnxt_re: Direct Verbs: Support DBR verbs Sriharsha Basavapatna
2026-01-09 18:35 ` Jason Gunthorpe
2026-01-13 17:13 ` Sriharsha Basavapatna
2026-01-09 18:50 ` Jason Gunthorpe
2026-01-13 17:13 ` Sriharsha Basavapatna
2026-01-09 18:55 ` Jason Gunthorpe
2026-01-13 17:13 ` Sriharsha Basavapatna
2026-01-09 19:01 ` Jason Gunthorpe
2026-01-13 17:14 ` Sriharsha Basavapatna
2025-12-24 4:26 ` [PATCH rdma-next v6 4/4] RDMA/bnxt_re: Direct Verbs: Support CQ and QP verbs Sriharsha Basavapatna
2026-01-09 18:37 ` Jason Gunthorpe
2026-01-13 17:13 ` Sriharsha Basavapatna
2026-01-09 19:08 ` Jason Gunthorpe
2026-01-13 17:14 ` Sriharsha Basavapatna
2026-01-13 17:27 ` Jason Gunthorpe
2026-01-17 8:07 ` Sriharsha Basavapatna
2026-01-09 19:37 ` Jason Gunthorpe
2026-01-13 17:15 ` Sriharsha Basavapatna
2026-01-13 17:28 ` Jason Gunthorpe [this message]
2026-01-17 8:07 ` Sriharsha Basavapatna
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=20260113172813.GS745888@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=andrew.gospodarek@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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