From: Jiri Pirko <jiri@resnulli.us>
To: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Cc: leon@kernel.org, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH rdma-next v9 1/5] RDMA/uverbs: Support QP creation with user allocated memory
Date: Wed, 28 Jan 2026 11:16:14 +0100 [thread overview]
Message-ID: <aXnh7rftc2DiZH_L@FV6GYCPJ69> (raw)
In-Reply-To: <CAHHeUGXpvj0owS6Z7Y53pxzf_MwT0EN6OdXqYN6Z-AbBXG4gVg@mail.gmail.com>
Tue, Jan 27, 2026 at 02:04:27PM CET, sriharsha.basavapatna@broadcom.com wrote:
>On Tue, Jan 27, 2026 at 5:42 PM Jiri Pirko <jiri@resnulli.us> wrote:
>>
>> Tue, Jan 27, 2026 at 11:31:05AM +0100, sriharsha.basavapatna@broadcom.com wrote:
>> >From: Jiri Pirko <jiri@resnulli.us>
>> >
>> >This patch supports creation of QPs with user allocated memory (umem).
>> >This is similar to the existing CQ umem support. This enables userspace
>> >applications to provide pre-allocated buffers for QP send and receive
>> >queues.
>> >
>> >- Add create_qp_umem device operation to the RDMA device ops.
>> >- Implement get_qp_buffer_umem() helper function to handle both VA-based
>> > and dmabuf-based umem allocation.
>> >- Extend QP creation handler to support umem attributes for SQ and RQ.
>> >- Add new uAPI attributes to specify umem buffers (VA/length or
>> > FD/offset combinations).
>> >
>> >Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>> >Signed-off-by: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
>>
>> When you send patch in my name, and you do some changes (patch
>> description was not present in my draft at least), I would expect some
>> off-list handshake. Is it too much to ask? Looks like you are in a big
>> hurry, that never brought anything good :/
>
>I didn't know you expected an offline handshake, since I was just
>updating the commit message (and that one other line I mentioned
>earlier). But please feel free to suggest/revert changes or if you
>want to push an updated revision yourself, I'm ok either way.
On which planet you find okay to take someones draft (untested) patch
from discussion, take it, add description and send it on his behalf, all
without consulting him?
I'm in a process of testing the patch. Give me day or two, I will send
it myself.
Thanks!
>Thanks,
>-Harsha
next prev parent reply other threads:[~2026-01-28 10:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 10:31 [PATCH rdma-next v9 0/5] RDMA/bnxt_re: Support direct verbs Sriharsha Basavapatna
2026-01-27 10:31 ` [PATCH rdma-next v9 1/5] RDMA/uverbs: Support QP creation with user allocated memory Sriharsha Basavapatna
2026-01-27 12:12 ` Jiri Pirko
2026-01-27 13:04 ` Sriharsha Basavapatna
2026-01-28 10:16 ` Jiri Pirko [this message]
2026-01-28 12:31 ` Leon Romanovsky
2026-01-27 10:31 ` [PATCH rdma-next v9 2/5] RDMA/bnxt_re: Move the UAPI methods to a dedicated file Sriharsha Basavapatna
2026-01-27 10:31 ` [PATCH rdma-next v9 3/5] RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function Sriharsha Basavapatna
2026-01-27 10:31 ` [PATCH rdma-next v9 4/5] RDMA/bnxt_re: Direct Verbs: Support DBR verbs Sriharsha Basavapatna
2026-01-27 12:30 ` Jiri Pirko
2026-01-27 14:15 ` Jason Gunthorpe
2026-01-27 15:07 ` Jiri Pirko
2026-01-27 15:56 ` Jason Gunthorpe
2026-01-28 10:04 ` Jiri Pirko
2026-01-28 15:33 ` Jason Gunthorpe
2026-01-27 10:31 ` [PATCH rdma-next v9 5/5] RDMA/bnxt_re: Direct Verbs: Support CQ and QP verbs Sriharsha Basavapatna
2026-01-28 15:32 ` Jason Gunthorpe
2026-01-28 15:51 ` Jason Gunthorpe
2026-01-28 18:03 ` Sriharsha Basavapatna
2026-01-28 19:41 ` Jason Gunthorpe
2026-01-28 16:54 ` Sriharsha Basavapatna
2026-01-28 17:57 ` Sriharsha Basavapatna
2026-01-28 19:42 ` Jason Gunthorpe
2026-02-02 14:19 ` Sriharsha Basavapatna
2026-02-02 17:48 ` Jason Gunthorpe
2026-02-03 5:05 ` Sriharsha Basavapatna
2026-02-03 8:57 ` Jiri Pirko
2026-01-28 17:58 ` Jason Gunthorpe
2026-01-28 15:46 ` Jason Gunthorpe
2026-02-02 14:19 ` 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=aXnh7rftc2DiZH_L@FV6GYCPJ69 \
--to=jiri@resnulli.us \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--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