public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Margolin, Michael" <mrgolin@amazon.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: <jgg@nvidia.com>, <linux-rdma@vger.kernel.org>,
	<sleybo@amazon.com>, <matua@amazon.com>, <gal.pressman@linux.dev>,
	Daniel Kranzdorf <dkkranzd@amazon.com>,
	Yonatan Nachum <ynachum@amazon.com>
Subject: Re: [PATCH for-next] RDMA/efa: Add CQ with external memory support
Date: Sun, 18 May 2025 11:56:56 +0300	[thread overview]
Message-ID: <985b77cc-63bb-4cf9-885e-c2d6aca95551@amazon.com> (raw)
In-Reply-To: <20250518064241.GC7435@unreal>


On 5/18/2025 9:42 AM, Leon Romanovsky wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Thu, May 15, 2025 at 02:50:40PM +0000, Michael Margolin wrote:
>> Add an option to create CQ using external memory instead of allocating
>> in the driver. The memory can be passed from userspace by dmabuf fd and
>> an offset.
> EFA is unique here. This patch is missing description of why it is
> needed, and why existing solutions if any exist, can't be used.
>
> Thanks

I probably should have explained more, the purpose is creating CQs that 
reside in GPU HBM enabling low latency polling directly by the GPU. EFA 
isn't unique in receiving pre-allocated memory from userspace, the 
extension here is the use of dmabuf for that purpose as a general 
mechanism that allows using memory independent of its source. I will add 
more info in the commit message.

Michael


  reply	other threads:[~2025-05-18  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 14:50 [PATCH for-next] RDMA/efa: Add CQ with external memory support Michael Margolin
2025-05-18  6:42 ` Leon Romanovsky
2025-05-18  8:56   ` Margolin, Michael [this message]
2025-05-20  9:16     ` Leon Romanovsky
2025-05-21 15:19       ` Margolin, Michael
2025-05-25 17:52         ` Jason Gunthorpe
2025-05-26 15:45           ` Margolin, Michael
2025-05-26 16:08             ` Jason Gunthorpe
2025-05-26 16:17               ` Margolin, Michael
2025-06-09 15:03                 ` Margolin, Michael
2025-06-11 19:47                   ` Jason Gunthorpe
2025-06-24 16:39                     ` Margolin, Michael

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=985b77cc-63bb-4cf9-885e-c2d6aca95551@amazon.com \
    --to=mrgolin@amazon.com \
    --cc=dkkranzd@amazon.com \
    --cc=gal.pressman@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matua@amazon.com \
    --cc=sleybo@amazon.com \
    --cc=ynachum@amazon.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