All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Anuj Gupta" <anuj20.g@samsung.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [RFC 2/4] nvme: let transports provide the dma-buf attachment
Date: Wed, 18 Nov 2026 11:37:43 +0000	[thread overview]
Message-ID: <sashiko-outbox-220832@kernel.org> (raw)
In-Reply-To: <20261118103327.1788667-3-anuj20.g@samsung.com>

> From: Nitesh Shetty <nj.shetty@samsung.com>
> 
> dma-bufs are currently attached to ctrl->dev by nvme-core. This works
> for nvme-pci, but fabrics transports can use a different device for
> data DMA.
> 
> Let transports create the attachment and pass it to nvme-core, which
> takes ownership of it. nvme-pci continues to attach to its PCI device.
> 
> Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com>
> Signed-off-by: Anuj Gupta <anuj20.g@samsung.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261118103327.1788667-1-anuj20.g@samsung.com?part=2


  reply	other threads:[~2026-11-18 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261118103434epcas5p4ddef3806fafdb60f309fe882e354881c@epcas5p4.samsung.com>
2026-11-18 10:33 ` [RFC 0/4] nvme-rdma: dma-buf backed I/O Anuj Gupta
2026-11-18 10:33   ` [RFC 1/4] nvme: move dma-buf I/O context handling to nvme-core Anuj Gupta
2026-11-18 11:36     ` sashiko-bot
2026-11-18 10:33   ` [RFC 2/4] nvme: let transports provide the dma-buf attachment Anuj Gupta
2026-11-18 11:37     ` sashiko-bot [this message]
2026-11-18 10:33   ` [RFC 3/4] RDMA/core: Add ib_dma_buf_dynamic_attach() Anuj Gupta
2026-11-18 11:36     ` sashiko-bot
2026-11-18 10:33   ` [RFC 4/4] nvme-rdma: support dma-buf backed requests Anuj Gupta
2026-11-18 11:57     ` sashiko-bot

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=sashiko-outbox-220832@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=anuj20.g@samsung.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.