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 v2 8/8] RDMA/bnxt_re: Enable app allocated QPs
Date: Tue, 14 Apr 2026 10:54:38 -0300 [thread overview]
Message-ID: <20260414135438.GC2577880@ziepe.ca> (raw)
In-Reply-To: <CAHHeUGVTsMSCrVQ2uSa4_1DfctNYL7Cy2y2QRPF67nW0mPFXzQ@mail.gmail.com>
On Tue, Apr 14, 2026 at 07:10:41PM +0530, Sriharsha Basavapatna wrote:
> > Yes, and it's fine, you added app_qp and the only thing it does is
> > check that userspace set VARIABLE. Why?
> No, app_qp (boolean) is used to make other decisions too. It is passed
> down to other routines and all that logic is in earlier patches (2-7).
> This patch just enables it.
So list what it actually does?
Jason
next prev parent reply other threads:[~2026-04-14 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 9:17 [PATCH rdma-next v2 0/8] RDMA/bnxt_re: Support QP uapi extensions Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 1/8] RDMA/bnxt_re: Refactor bnxt_re_init_user_qp() Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 2/8] RDMA/bnxt_re: Update rq depth for app allocated QPs Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 3/8] RDMA/bnxt_re: Update sq " Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 4/8] RDMA/bnxt_re: Update umem " Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 5/8] RDMA/bnxt_re: Update msn table size " Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 6/8] RDMA/bnxt_re: Update hwq depth " Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 7/8] RDMA/bnxt_re: Support doorbells " Sriharsha Basavapatna
2026-03-27 9:17 ` [PATCH rdma-next v2 8/8] RDMA/bnxt_re: Enable " Sriharsha Basavapatna
2026-04-10 15:27 ` Jason Gunthorpe
2026-04-14 6:13 ` Sriharsha Basavapatna
2026-04-14 12:34 ` Jason Gunthorpe
2026-04-14 13:40 ` Sriharsha Basavapatna
2026-04-14 13:54 ` Jason Gunthorpe [this message]
2026-04-14 14:06 ` Sriharsha Basavapatna
2026-04-14 14:19 ` Jason Gunthorpe
2026-04-14 14:34 ` Sriharsha Basavapatna
2026-04-14 15:09 ` Jason Gunthorpe
2026-04-14 15:14 ` Sriharsha Basavapatna
2026-04-10 15:25 ` [PATCH rdma-next v2 0/8] RDMA/bnxt_re: Support QP uapi extensions Jason Gunthorpe
2026-04-14 6:13 ` 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=20260414135438.GC2577880@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